You have a fundamental misunderstanding. There is no difference beyond UI wording. Read about Events and States here: Introduction to Automation
You are free to do whatever you want, but this is not a real solution.
There are no such events reported by the hub to act upon. You could write custom drivers to do this, but trust me, you won't like the result. And, it's a huge waste of effort. If you are having to go to these contortions for your use case, you are using the wrong tools, as well said above by @coreystup.
If you want industrial grade automations, then you have to use industrial grade devices. These exist, are not cheap, and could be controlled by Hubitat. As long as you have flaky consumer devices, you're stuck with a bad fit.
If my hub gets fooled by a light being in the wrong state, maybe the light won't turn on when it should, or will stay on when it shouldn't. Such a failure self corrects on the next cycle. I'd guess this happens at a rate of less than 1 in 10000. The light not turning on has a super easy fix, hit the light switch. Attempting to take "home automation" beyond this expectation is not a smart move, imo.
