That's quite a leap to say that because they don't invoke any restrictions until you cause problems, they must be "underconfiguring and dumping the blame on a user".
You configure your systems -- any systems -- for a certain level of utilization by your users. You monitor them for when they exceed the level you intend.
If you handle the case where users occasionally cause the capacity to be stretched by enforcing the well-known limits, or by causing everyone to degrade, well, that happens.
If you do it by spanking a user for mysteriously being a bad citizen, when he's doing somethjing you permitted and worked fine the day before, well, that's just bad customer relationship management.
Admittedly, I'm not a big user of the batch system. But I'm not sure I get how a rate limiter that only comes into play when you are beating the ever-loving spit out of a system is necessarily a bad thing.
IF you tell people what the rates are, and LIMIT them, fine.
If you tell people that they will be throttled in the event of resource conflict, fine too -- though if you see it repeatedly, it's time for more resources or hard limits.
If you suspend a user for overusing a resource without defining overuse, not fine.
