It is currently (ab)using the screen BlockHandler callback to do this. But this can cause problems with other extension as their block handlers might have executed before Composite's. And the operations Composite does might result in them wanting to change timeouts.
Practically this caused problems for TigerVNC's VNC extension which failed to send out updates for Composite's screen updates.
Original bug report in bugzilla: