Specific visibility options during Playback

Situation

There is often a difference between what you need during playback vs the rest of the time.

People work with complex scenes containing guide objects, controller bones, boolean shapes, and more-or-less dense meshes that are useful while you work on them, but create visual clutter or impact performance during animation playback, or incorrectly represent what you'd want to see while previewing in motion.

E.g. bone controllers, lattices and boolean shapes are almost always useless during playback. Subdivision levels could be lower during playback too.

Currently, these elements remain visible during playback unless manually hidden beforehand, which interrupts workflow when switching between working and previewing, and makes it more tedious.

It's also somewhat unpredictable when it comes to Viewport or Workbench rendering, as certain things are arbitrarily hidden during the render, with no clear queue about it and no control over it.

We can also see that now when using Compositing or the VSE, we need performance during playback but some nodes or filters really hit the performance.

Solutions

Similar to how most things have dedicated controls for viewport vs render visibility, we could introduce a playback visibility.

Objects, collections and modifiers could be individually set to be hidden during playback.

But we could go even further:

Modifiers could also have dedicated settings relevant for them. E.g. The Subdivision modifier could have a Playback subdivision level:

Think of other modifiers like array, decimate, multires, ...

Geonodes and Shader nodes could have a node to give Playback state.

The Selectability And Visibility popover could have a playback visibility too:

Perhaps other areas could benefit from that too. Like render settings , compositing nodes, VSE strips (and strip effects).

None of these would impact rendering on Eevee or Cycles. But it could impact Viewport/Workbench rendering:

Finally, also implement this for all overlays. So that not only we can do things like hiding performance-killing or occluding overlays in playback like the gizmo, outlines, origins and whatnot, but also we make the viewport and workbench render engines fully predictable and user customizable.

Though this seems more complicated to implement, at least GUI and UX wise: i don't think adding playback buttons along every overlay checkbox will look and feel right, hence I don't provide a mockup for this.