We need a general sensor setting or helper for rate limiting sensor updates

All too often these days things are moved from YAML configuration to an integration and in the process you can pretty much guarantee that support for scan_inteval is dropped and usually, there is little to no rush in fixing that. The only way (that I know of) to fix this is creating template sensors and excluding the original sensors for the databases, but that is a real chore when you have a long list of sensors that are updating too fast. A general quick way to manage rate limitation for sensors would be great.

This already exist for all polling integrations https://www.home-assistant.io/common-tasks/general/#defining-a-custom-polling-interval

You’re right. Completely forgot about that one. To my defense, it IS a very unintuitive way of doing it.