So, it's more like a management problem. You, or they, or whoever takes place in a proyect, don't change something like that because you feel like doing it, or you shouldn't, I fear.
If I was you, I'd make a naming scheme and share it to the whole team, so everyone accept that, because that checking you want to do is entirely for develop purposes and, as I understand, it shouldn't change anything in your implementation's logic. It'd be better to spend a little more time in design than thinking how to implement something you shouldn't need.
Given that scenario, anything can happen, and thus any action would be futile, since that thing you want is not featured by Playmaker. It seems that is not enough to store events as variables, although you could do it, but then, which variable would refer to which event that defines a specific transition? But, if they change an event name, your only problem is if you hardcode the names and use them for any logic, since Playmaker will change that name wherever it's used. The best I can say now is... Avoid hardcoding event names, or if you need to do it, agree with your team a naming scheme.
Greetings.