Does the "brand" include the physical shape of the connector?
Could I make hardware with a "NotHDMI" port that "happens" to be mechanically compatible with HDMI plugs, has the exact same pinout, etc etc?
Even then: In the OP case the hardware is already there, it's only about the driver. So wouldn't a driver for hardware that very clearly identifies the port as "HDMI" run into the same problem, even if the driver itself never mentions the term?
It's not impossible to do things, but people (in the US) are extremely resistant to any kind of perceived change or self sacrifice.
It's a common story for any kind of infrastructure project in the US.
I'm personally not a fan of her policies. Tax cuts won't solve the fact that Japan still has one of the highest debt to GDP in the world, and will only make the Yen weaker in the global economy.
Sometimes, you have to rip off the band-aid (Low taxes) in order to get better (stronger Yen).
See, companies that deal with a lot of traffic on static data have geographically distributed caches.
Let's say Steam has a major game release, and gets slammed with the DL traffic of 5 million gamers all around the world trying to get their hands at that new game all at once. However, Steam has an instruction manual that allows any ISP to set up their own cache servers. So an ISP that has a cache set up can convert a lot of that global traffic to local traffic, saving them money, and offering users a better experience.
(One small ISP I knew had it set up so that all traffic to their local Steam cache was fully exempt from client rate limiting, reportedly because the ISP's admins were avid gamers.)
Other services like major CDNs, YouTube or Netflix may have deals with ISPs to locate their caching hardware on ISP premises, or may buy their own caching servers in specific datacenters. Same idea applies - it's cheaper for both ISPs and web services when the users hit local caches than when they "cache miss" and generate global traffic.
VPN use is a "forced cache miss", so it's a loss-loss for both ISPs and web services.
Disclaimer: Former YT Engineer.