A suggestion for the Visual LISP route: how about using a Command Reactor with a call-back function triggered on the :vlr-commandwillstart event to record the necessary registry keys when the 'Options' command is used; then, another call-back function triggered on the :vlr-commandended event that will check those same keys against the cached values to detect any changes.
Just an idea | Untested.
That is almost the exact methodology that I have been using prior to posting this thread.
The problem being, as I see it, that it's inefficient in that it monitors all instances of the user issuing the OPTIONS command, _and_ either has to monitor all LispWillStart events, or knowingly leave open a back door (by not doing so), as LISP can also change these Properties.
That can be done, but it seems like overkill for what I see as such a small, yet intuitive task.
That's also a nice idea Lee! Though it's still going to make RM's day searching for all the envars and/or registry keys 
Actually, if I go with the pure Reactor route, it's easier to programmatically Set the appropriate values upon *WillStart events, than teaching myself how to _properly_ use Delegates, and Event Monitors. LoL It's just unnecessary burden on the end-user's processing time. LoL
I appreciate everyone's assistance!
