Problem
All events (eventhandlers, display (key) handlers etc), and conditions (e.g FSM, trigger condition etc) in ArmA are unscheduled, but spawned script instances are scheduled, as well as the states in FSM.
Scheduling is disasterous for interactive features, like steering a vehicle (parachute) etc, on top of the fact that sleep time isn't a (reasonable) constant anymore, but in fact a variable,
that will need to be taken into account in the calculations of effects.
Still, for interactive systems, a combination of event-based (handling the interactivity), and loop (scheduled script instance, handling general processing), might be a solution to the problem.
Measuring
Enabling the diagnostics addon: In the main @CBA folder called: "cba_diagnostic_enable_perf_loop.pbo"
Copy the PBO to @CBA\Addons folder, start the game and run the tests you usually do.
Please let the mission run for at least 15 more seconds after testing is done, to make sure all log entries are written to rpt.
Then check the rpt and share it in a ticket, so we can read back the results.