I've also noticed that when a step is running it may show larger value for the duration that it does after it is complete.

That seems pretty bad.  Milo uses numbers emitted by the recipe engine for steps, and then timing data from swarming to determine the final start/stop time.  There's probably extra overhead that's significant and unaccounted for.  Maybe we can add those visualized as steps.