Perhaps it's not helpful for the moderator, but it's not meaningless as a whole. It helps people viewing the run, those that assume the speedrun timer is correct/accurate when it might not be. People can only work with what is presented to them. The more accurate information the better. If you only present a speedrun timer with an offset from the actual time, that is the info most people will receive.

In my opinion the runner should add a timer in their video editing software before publishing the run. Start a timer on the first frame and hold the timer after the last frame. Splits are only an approximation and guideline to the runner and stream watchers to how well a run is going, it's not a conclusion.

Example:

Start running the game again guys, so we can have some fun. ;) With perfect execution and the 3rd bonus skip on stage 31, or earlier it should be possible to get sub 7:35.

You might want to sett up some rules for the runs though.

The out of the box settings for WinUAE 4.3.0 are pretty decent for emulating A500 and there should not be any speed issues unless people start changing parameters where they shouldn't. All that should be touched is location of the kickstart ROM, directory locations, screen/window resolution and controller keymapping. If "cycle-exact" should be used is debatable. The easiest solution is either a configuration file or mandatory settings/configuration guidelines.

Stage 14 is too late for bonus 0 if you want 3 bonus skips throughout the run.

Cutting loading times is a really bad idea and will prevent the best possible runs from taking place. Just require WinUAE to run at Approximate A500 CPU Emulation Speed and 100% floppy emulation. It should be fairly consistent.