Option to prevent Tasker recognising state profiles being enabled/disabled as states being entered/exited

Currently, if a task enables or disables a state profile while the relevant state condition is satisfied, Tasker recognises the state as being entered or exited. E.g. given a profile state %Var ~ true, if %Var is indeed set to 'true', disabling the profile triggers the associated exit task, even though %Var is set to 'true' still. The state has not been exited. While this may be useful at times, it's surprising behaviour, and if you're not aware it's how profile states function, it's difficult to isolate as the source of tasks not performing as expected.