Following up from WICG/interventions#5, WICG/interventions#9 and WICG/interventions#34, we should explore to what extent "clamping"/aligning and throttling timers under various conditions (background tabs, out-of-view and/or cross-origin iframes) is supported in the spec. This is useful for perfomance and power efficiency by reducing CPU wakeups, and it's implemented in all major browsers, as evident in the linked issues.
It might also be worth defining minimum/maximum wait time boundaries that developers can expect their code to run in.