NOTE: This is NOT meant as a continuation of the debate. Not trying to press my argument with this particular inquiry; this is merely my admittedly unreasonable (it's not my fault; I was born this way lol ) level of curiosity coming out...
A future, possible scenario occurred to me, and I want to walk through it here, and get your input (if you're willing; no expectation. TL;DR...).
At least one instance of this SmartApp
Create a new, dedicated Mode just for this SmartApp's disabling capability
Configure this SmartApp to use that dedicated system Mode as a disable mechanism
Configure all other like-equipped SmartApps to each also use their own, dedicated system Mode (created by the user; specifically for this purpose) for disabling capability
Regardless of the Mode Scheme in place in the SmartThings infrastructure being worked on, and regardless of what Modes the SmartApp is currently configured to be 'active' in, configure all so-capable SmartApps to also be 'active' in the Modes of all of the other so-configured SmartApps
In a troubleshooting or testing session (unrelated to this tstat app), in an attempt to isolate/eliminate a particular SmartApp, the user changes the Mode of their system to the dedicated Mode for that particular SmartApp instance.
If the system is changed to one of these SmartApp Disabling Modes, what would this RBoy Tstat SmartApp do during the time that the system is in that particular Disabled SmartApp Mode?
What if the user's troubleshooting or testing session continues beyond the time boundary of the next scheduled Mode Change, and the user isn't aware of the time? Will this RBoy Tstat SmartApp change the Mode of the system to the one that it is normally scheduled to change to, or would it sit idle, and leave it going with whatever settings it had from the most recent Mode change before the system was put into the Disabled SmartApp Mode?