Thanks all, for your replies with helpful details.
Several successful setups in a broad range of cost confirms what we already suspected, that the software and hardware driving the USB-port, plus the disk write speed, are the essential factors when imaging with high frame rates. Not so much the CPU/GPU/RAM/etc.
Not sure if you ever would encounter a (rather) new laptop with well performing USB 3/3.1 port that would not do the capture job well, due to weak processor etc. (disregarding image processing here)
Guess we could ask the makers of Firecapture/Sharpcap, if ever needed.
In the meantime I bought a new "medium class" Acer Swift SF314-51-56Y4 with i5-6200U, 8GB DDR4 RAM, 500GB SSD Liteon CV3-CE512 read/write 520/440 MB/s.
Got max framerates as announced for the 1600MMC and the 290MM, will post back if not also for the 174MM that will arrive soon.
Must say it is great to also have a USB-C port in laptops these days, very helpful for mobile imaging with an USB-C hub and support for USB Power Delivery, while running big USB 3.1 disks like they were fast internal ones.
Oh, did a quick check of today's for disk write speeds. Still, the SSDs for laptops, even the insanely expensive ones, do not have a fast write speed compared to conventional hard-drives.
I could get an SSD with 5% faster write speed for about 5 times the price. (some sticker..)
But it seems that an average external USB3.1 conventional SATA-600 disk would win this competition by a good margin both in terms of write speed and cost. (assuming top USB3.1 performance)
But don't take my word for it just yet. Might be factors that I don't know about. (e.g. frequent read operations in between, that may favor an SSD after all)
The statement seen around, "you need a big and fast SSD for planetary imaging", might me a bit of a misconception, and you could save a lot when going for huge storage.
Doing a check was worthwhile for me. At times I go to dark sites in the mountains, using two or three setups at the same time (most DSO, some planetary), one laptop for each mount, and one at a field table for remoting.
No need to give the "dumb" mount-laptops unnecessarily expensive hardware :)