On a positive note, I very much suspect the USB-C connector of being miles better than the Micro USB 3.0 interface my current caddy uses. In my experience, a bit of external force can easily encourage the connector out of the port.
> (and a random £15 caddy is obviously not going to provide very good competition.)
P.S. re this, I can sort of understand it, as the caddy came with a drive -- they clearly had the opportunity to optimize away support for filesystems that they weren't pairing the caddy with.
[0]: https://www.amazon.co.uk/SABRENT-enclosure-indicator-tool-fr...
https://www.amazon.co.uk/SABRENT-enclosure-indicator-tool-fr...
I'm a bit confused, but isn't eSATA exactly what you are looking for?
※ Listed on Amazon as "SABRENT 2.5-Inch SATA to USB 3.0 Tool-Free Clear External Hard Drive Enclosure [Optimized for SSD, Support UASP SATA III]"
From what I understand, many eHDDs don't actually do this, instead reading the contents of the drive and exposing them to the computer by essentially emulating a USB flash drive. I would have to sniff the packets to be sure, but this is what I suspect my eHDD caddy is doing.
My main reason for wanting this is that, in some cases, it would make reading random drives substantially easier -- I have amassed a collection of HDDs that all have different partition schemes, filesystems, etc., and a fair number of those are unable to be processed by my caddy. This is a very frustrating experience, as a Linux device has some of the best filesystem / partitioning support in the world (and a random £15 caddy is obviously not going to provide very good competition.)
On the contrary, having the kernel process the HDD as a block device would most likely place it under marginally more computational stress (as opposed to the drive reading partition tables and filesystems itself), but I believe that's been fairly well-optimized by now.