Sorry about the delay, things have been busy around here. I responded to your report and am including the same message here so the thread isn't left hanging.
I contacted Vengeance Sound for copies of these plug-ins and it's clear where the confusion comes in with automation. SONAR applies the value of the very first automation node from the beginning of the track until that node's position in the project timeline. This behavior works well for most parameters, like track volume or EQ settings. For the Tape Stop "Stop" button and Glitch ****'s "Glitch" button, however, this behavior winds up applying the plug-in's stopped or glitching behavior too early, as you found.
In order to get around this, simply add one automation node in the "off" position directly in front of the first "Glitch" or "Stop" automation node. As you know, you'd want to place this node at the bottom of the automation lane to trigger the "off" position of the Glitch or Stop parameter. (This is the same suggestion you received from Rene Keilwerth.)
I understand that doing this would be an extra step in your workflow. But, unless it's possible for these plug-ins to reverse the value that the "Stop" and "Glitch" buttons record while automating them, please add one node to the "off" position of this automation lane.