that's not really much of an argument, almost all reasonable libraries wrap the functionality.and if a provider doesn't want to support http3 then the library will fallback, and then the laggards should pay the slow tax.

No as in the infra between you and the end user is less developed.

Nobody is going to get fired for using http1.1

if you move to http3 and a bunch of clients cant use your site, then you're gonna get yelled at.