On Windows, a USB device's configuration is tied to its port, so by using this hack the device's settings will change depending on the orientation of the connector. This can't be good for user confidence in USB-C.
https://devblogs.microsoft.com/oldnewthing/20041110-00/?p=37...
For instance, I used to work on a project where I needed to control multiple Epson thermal printers from a single Raspberry Pi. Each printer was assigned to a customer kiosk, so I needed to know where I was sending the print job to. Unfortunately, the Epson thermal printers did not expose any unique ID over USB, so I had to rely on the USB device enumeration, and I label my cables and printers accordingly.
A USB-C port like in TFA would cause extra headache.
Also, a device’s settings that depend on the port to which it is connected is terrible UX.