bring back longer polling intervals (e.g. 12 hrs, 24 hrs)

For use cases other than performance metrics, it may be worth considering a PropertySource or a ConfigSource (if you have LM Config).

A PropertySource will run once per day and set/update one or more device properties, which could for example list or count the outstanding updates at that time. There is no graphing or alerting directly, although a DataSource could then pull the property value in, e.g. if your PropertySource produced a count of outstanding updates. In that way, the "hard work" - i.e. the script to find the updates - runs only daily, while the more frequently run DataSource does very little / causes very little load. Textual property values can be pulled into Device Inventory Reports.

For direct alerting, LM Config permits a ConfigSource to be run every 1, 4, or 24 hours, and you could have it generate alerts on any change, e.g. when the list of outstanding updates changes. Again, no graphing, but in many use cases a graph is not as vital as having the textual data.

With an hourly config collection you could also script in the time limitations, e.g. only collect a config if the hour is 3am.