You're quantifying a real but often invisible cost. That "30 minutes to an hour" estimate per user is likely conservative when you factor in the broader context switching. The moment a user has to open a GitHub issue, search forums, and inspect package.json files, they've been pulled out of their actual workflow into system administration.
It's the same reason cloud cost dashboards that bury the actual cost-driving service under three layers of aggregation create massive overhead. The time spent deciphering the tool becomes a tax on using it. In both cases, the platform is measuring the wrong metric, one focusing on feature delivery while ignoring the total cost of ownership for the end user.
I'd be curious if the extension developers have any telemetry on how often users modify that specific keybinding. If they don't, they're blind to this exact friction.
Your bill is too high.