Nobody is writing slow code specifically to screw over users with old devices. They're doing it because it's the easiest way to get through their backlog of Other Things. As an example, it is a priority for a lot of competitive games, and they perform really well on everything from the latest 5090 to a pretty-old laptop integrated graphics GPU. It's done not because they only hired rockstar performance experts, but because it was a product priority.
From a Danish perspective I think that this is rather cruel.
The statutory protection for H1Bs is thin. In 1990, Congress excluded H1B from the requirement applicable to other non-immigrants that they retain a foreign residence, and from the rebuttal presumption that someone who applies for a green card has immigrant intent. That’s it. The common operation of H1B as being an immigrant-intent visa is mostly a matter of administrative grace.
I think it's reasonable to have attestation for the corporate use case. If they're buying security devices from a certain vendor, it's reasonable for their server to check that the person pretending to be you at the other end is using one of those devices. It's an extra bit of confidence that you're actually you.
~~Have you considered a copyleft licence like LGPL?~~ Answered in a sibling comment
Expecting a reward from open source software is a recipe for disappointment. I have contributed code to projects by companies that say I'm a mentally-ill household object. I'm not going to change the license of my open source projects to get back at them, because the collateral damage against entities that aren't evil simply isn't worth it. (It's also somewhat unlikely that the people working on NTP servers at Facebook wrote those policies, so...)