Tech_TTT :
The Central PC (Switch ) will have the USB3.0 ports on CPU lanes and not the chipset one, to avoid DMI3.0/2.0 Bottleneck .
The other Pcs will use the on board USB3 ...
if this works , I will move to USB3.1 after that .
This 5Gb/s will not even be shared ... the backbone will be (number of USB3 X 5Gb/s )...
There is a large difference between this card:
https://www.amazon.com/Rosewill-Express-Expansion-Connector-Renesas/dp/B011LZY20G
And this one:
https://www.amazon.com/Express-SuperSpeed-Adapter-Dedicated-Channels/dp/B00HJZEA2S
The first one (by far the most common and also how your motherbaord ports are configured) SHARES the 5gbps bandwidth accross the 4 ports. The second card has the bandwidth to have 4 independent 5gbps links.
Us "idiots" with jobs, certifications and businesses in networking have to have education and knowledge in how the TCP/IP protocal and the rest of the OSI model actually works and that trying to fake it over USB cables is no easy feat.
A USB to Ethernet Driver works because it is written for the chip in the adapter, its not like they just took the 9 pins of wires in USB 3.0 and wired it to the 8 pins in an RJ45 jack. Thus you cant just take TP-Link's adapter driver and use it for your adapter-less USB 3.0 cable and poof you have a "network connection."
Driver aside, with no real ethernet adapter (and nothing providing DHCP) you will not only need to manually setup a unique IP address for every USB 3.0 port being used for this on the NAS and on each computer, but ( unless the driver does it for you) you will also need to make a bogus physical address for EVERY one of those connections as well (this is a required part of all ethernet packets at layer 2)
What you have to realize is that your entire idea hangs on the hopes that someone else (not you) has written a USB driver for just a cable (not one with an ethernet nic built into it) to create an ethernet network connection with full support of TCP/IP.
This is just for the "it works' not even real world speeds or stability.
With that said it is certianly possibly that someone else has develped a USB 3.0 driver specifically for just a cable., this used to be "common...ish" with USB 2.0 male to male cables to transfer settings between computers in the windows XP/Vista days. Although this was more of a serial protocal connectoin, not ethernet.
Also, FYI considering you are forcing a driver as something it is not, dont be supprised if major windows updates require this to be completely re-setup.