I would consider option 3
And see this as a “mute” or “bypass” - where input signal passes through unaffected
Switching it on and off then lets you quickly see the difference, with or without what the node does
use case :- switching windows to fullscreen, when using 2 to 4 screens showing various bits of the composition on each, sometimes as one single canvas across all outputs... (using Mac mini + sonnet egpu, Mojave, Vuo 2.0beta2 <= but this issue appears to be the same in Vuo 1.2)
so the logic seems to be, for a window to go fullscreen on a specificitic monitor, it needs to already be positioned on that monitor AND be active (selected), - then it goes full screen on that monitor when it gets a fullscreen true property..