Re: Inquiring minds want to know...
Windows doesn't actually move the "deleted" file to the bin, rather it links to the deleted data from the bin. The bin isn't a single physical location, it's a virtual space that stores links. With that said, there used to be a utility that allows you to do what you suggest. I can't remember its name, and I have no idea if Win10 would even allow such a thing ... Keep in mind that physically moving the data from disk to disk on deletion will increase filesystem overhead tremendously.
But you are onto something. Proper use of disk spindles and partitions. When I setup my one remaining Windows box back in 2000 (yes, twenty years ago), I did it like this:
OS on controller1, spindle1, partition1 (with a bootable backup on partition2) ... Registry on controller1, spindle2, partition1 (with a rolling, usable backup on partition2) ... Swapfile and tempfiles on controller2, spindle1, partitions 1 and 2 (WinSwap can also be used as a Linux swapfile, but that's another story) ... and last but not least, user data on controller 2, spindle 2, partition1 (odd day backups to partitions on the other three spindles, external backups on even days, off-site backup on Sunday).
The OS isn't slowed down by the second drive (spindle) being accessed or written to for registry contents, and the swapfile and temp files are rarely called for by the OS at the same time. User data being on its own spindle just makes sense. The whole kludge separates the cluster-fuck that Windows insists on for its filesystem into four completely separate drives.
It's ugly, but it works. My old installation of Win2K has never once crashed, lost data, or otherwise given me any file-system headaches in 20 years of near daily operation. (I've physically lost drives, but that's a hardware issue not a file system logic error ... and I've always been able to recover quickly with the above setup.)
The old girl is airgapped, so fuhgeddaboudit.