it didnt answer your question(s) at all. there was no mention of intent for their algorithm.
The intent of the algorithm is to be as aggressive as it can in keeping you safe without being annoying and inflating because you forgot to turn it off and you dropping it on a chair, while keeping them out of a lawsuit because it didn't go off when "it should have".
I would expect it to go off on anything that is more aggressive than a bit of a tank slapper. I'm pretty sure anything that has you off the bike, and/or on the pavement is considered a "crash".
The amazing thing about this incident is how it decided to NOT react when the rider was separated from the bike, but, rather, later in the sequence. It's not like it didn't know they rider was flying, but it also probably figured "well, if he's flying, he's got to land, so may as well wait a teeny bit and deploy closer to that".
it's also why they have "race" systems and "street" systems, and the environments are different.
But in the end, the simple truth is that the system can detect and react in microseconds. Consider the $100 insurance. How many times does the system have to go off false positive to earn its keep when it does fire to save your bacon.