Better benchmarking of internal processes

For example, during a path it might be interesting to see which movement types consistently underestimated vs overestimated how many ticks they would take.

Also, I think a warning of when the onTick handler took more than X milliseconds would be helpful, same for renderFrame (but in nanoseconds).

Start by locating the path movement-type tick estimates and the onTick and renderFrame handlers mentioned in the issue. Determine how benchmarking results and timing thresholds should be represented, then verify that movement estimates can be compared and warnings appear when the requested limits are exceeded.

Written by the indexing model from the issue text.