Maybe I don't explain myself right.
Executing the same state n times with a loop count is better, we agree, but if the loop is going to be executed, say 10 times, it will take 10 frames long. 20 times, 20 frames long etc...You can never execute a state with a loop count many times in one frame...you can do it with lots of PM actions, but not when one of this actions is a Raycast.
Somehow, raycast always prevent this loop to be executed in a single frame, even if "repeat interval" is zero.
In other words, the Raycast action works like a "next frame event"
I just wonder if a custom action could do this...or maybe there is some kind of limitation I don't understand.