Canton ledger pruning: Request Frequency of Time-Proofs

IIUC as per the docs here, canton.domains.mydomain.time-tracker.min-observation-duration = 1h makes the participant nodes, mediators and sequencer request time-proofs every hour instead of just once per day. Are there any reasons why this may be a bad thing to do and is hence not the default time-proof observation interval?
Or is it more that it is simply not needed since pruning retentions are usually > 24h?

The min-observation-duration setting involves a trade-off between avoiding unnecessary churn in the system and being able to prune relatively recent data. The default of 24h reflects an assumption that customers typically don’t prune data more recent than one day and that thus a lower setting is typically “not needed” in production settings. In some of our test environments with lower space capacity, we also lower the setting.