No, without tracking the second variable, the condition gets evaluated every frame. I don't want to do no-op DOM updates every single frame for as that'd be incredibly wasteful. I'm just going to keep it the way I have it and consider it a shortcoming of construct I'll have to work around.
This is as clean as it's going to get I guess...