To be honest, I'm not really sure why this is necessary. I don't see why couldn't have two interfaces - one simple/moderate-speed one for most use cases, and a fast one (which could incorporate the slower one) for when it's needed. Trying to cram everything into one interface seems to introduce too many compromises (I no longer know what the port does) and a lot of complexity.
the point is you shouldn't have to know what the port does, it should seamlessly interconnect. you shouldn't have to be thinking about wires etc. it's like how bluetooth somewhat seamlessly interconnects across generations of bluetooth. that's how all standards should be
