In practice, I don't find the 'push' of Vuo to be problematic, and if anything, is a little more intuitive than QC.
I think there's two aspects here:
Issue here from ooftv which is common to me—the desire to turn some layer, or processing on or off, which requires an additional two patches or more—in the case of a layer, I find I need to create a layer of 0% opacity and switch to the input (since simply turning off the layer doesn't remove it from the rendering layer stack)
Efficiency, and knowing what nodes are running or not, and at what frequency. I think a neat solution for #1 might also solve a lot for #2.
How about just /? My reasoning being that comments are important in any kind of coding, and should be easy for the user to add.
Many creative apps (thinking off the top of my head) Photoshop, Figma, Sketch, Screenflow support un-modified key actions for common tasks. For example, 'o' is the circle tool in Photoshop, and 't' performs a trim in Screenflow.
Just last week I built out some animated stings for use in a video, made using Vuo.
I used the Image Generator protocol Edit>Protocols>Image Generator.
This lets you render really high quality anti-aliased, motion blurred alpha channel content. I used H.265 with alpha channel. Motion blur makes stuff look :chef kiss:
Jean Marie Does Vuo know not to run video through the Posterize node if, downstream, it's not used?
I know Quartz Composer used bottom-up rendering to achieve this efficiency.
In any case, you can avoid this particular problem by structuring so you use a Choose Output instead, and use a Select Latest node to, well, take only the latest and greatest.