Moving forward we will switch our timing method for PC runs to Real Time without loads. Thanks to the seperation of consoles it is easy to set it up for every PC run without having to worry about how to handle the same for consoles. We use the Load remover built into Livesplit. For the settings of the load remover: Check the top four options, the two below (Pause on Any Key Events and Pause while game is inactive) are not allowed and will get your run rejected. They might get removed in the future. The defaul options should cover this. For setting up the load remover correctly, refer to the forum post about it: https://www.speedrun.com/bsrotn/thread/jv3hc . If you still have problems setting it up, just ask :-) For any run that doesn't use the load remover we will treat Time with loads as Time without loads, so make sure to set it up correctly and have it on screen for your submissions! The unfortunate side effect is that all previous runs get worse to not having removed load times but I'm sure you all can improve on your runs anyway :-) For console runners nothing changes, we still use normal RTA timing, please just leave the "Time without loads" field empty for your submissions.

So, when using this, do we have to re-time the run to get the time with loads as well to include with run submission?

You can edit your split layout and add a secondary timer next to the original timer, then have one compare against Real Time, and the other compare against Game Time. You can also just right-click the splits and click on Compare Against -> Real Time. I would recommend the dual timer method, because submissions are required to have the loadless timer visible during the entire run until completion, so the two timers visible at all times rules out any mistakes with the timer that could possibly invalidate your loadless times.

Time with loads is not even absolutely necessary to submit as it plays no role on the leaderboards as long as you have a loadless time. You could also leave time with loads empty. And of course its easy to retime afterwards anyway.