OK- i looked into it. The Release function only exists on switches that have a HOLD function as secondary, since this is the only way for the switch to determine whether you meant Tap or Hold.
In my FC Layout for scene change there is no secondary HOLD function to the Scene change Switches, so theoretically, or at least according to the manual, the change should be taking place as the switch is depressed, not as it is released...
So that its not the reason....
I think Cliff is probably needed on this topic as it is a deep programming topic i am being led to believe.
I purposely made a preset near naked so to eliminate another causes.
In the scenario i am presenting the only change introduced in the Scene change is an added Drive block, while all the rest remains the same, yet a latency in response is introduced.
While no Latency in response is introduced when im adding that drive block within the same Scene, so exact same effect, 2 methods of getting there - one with latency in response, one without.