Apologies for the delayed reply, and thanks for taking the time to put together such a detailed report.
We can confirm this is a known issue and it’s on our list of planned improvements. We were hoping to include an improvement for this in Scaler 3.3.0, but unfortunately it didn’t quite make it into the release.
It’s still on our roadmap, and we’re hoping to address it as soon as possible in a future update. Thanks again.