There's no lobster rolls stuffed into a backpack here. It's using the service as it was pitched, an all-you-can-eat buffer of API calls. Anything that limits what that means is scaling back access to that buffet.

If the new limits are anything less than 24 * 7 / 5 times the previous limits then power users are getting shafted (which understandably is the point of this).

What's worse with this model is that a runaway process could chew through your weekly API allotment on a wild goose chase. Whereas before the 5-hour quantization was both a limiter and guard rails.

No it's not. It's like an all you can eat buffet stating you can eat as much as you want and feed your friends and the homeless outside for a one time fee, and then realizing that the economic model made 0 sense to begin with and need to either state that you're only allowed to eat what you personally can, or increase the price to something that can sustain the amount of food being removed from the buffet.

The fact you believe the 5% number is pretty interesting.