Your "solution" is interesting, but not ideal - in fact, it is "breaking" the "Integer Changed" so that all
values pass through (even when no change).
Hard to explain quickly, but it works something like this...
1) Value changes - blocker at input stops triggers going many places.
2) Trigger does get to the Trigger Switch.
3) Trigger switch sends a special "Backwards" trigger from boolean input - this forces the Not/Equals etc. to update value calculated from current input.
4) "Backwards" triggers will pass through Trigger Blocker - so if values are the same, the "true" from the Equals will be seen. If not the same, "true" value from Not will be seen.
5) X OR (NOT X) = Always True, so the Trigger Switch will never turn off.
6) Integer Changed now has no effect, all triggers will pass.
The idea of "Backwards Triggers" is very confusing - and not explained well in the user guide etc. You can find HERE
a guide I wrote about this - Sorry, only in English, but many diagrams may help understanding.