On NSMB2 Load Times

You probably got here from the speedrun.com rules, so I don't need to explain how this is about load times. So, here are some questions you may have, and answers to them, explained in as much detail as possible.

The game has differing load times?
Yes, but only when the system the game is being played on is homebrewed*. The game loses 17 frames per load (9 on new3DS) when loading a level or loading the world map, and loses 4 frames per load (saves 2 on new3DS) when entering a pipe, door, or similar object.

What counts as "homebrewed?"
Your system is considered homebrewed if it has boot9strap (or arm9loaderhax) and luma3ds installed, and is running on a separate emuNAND. It's complicated, but basically if you or someone else hasn't done the process here: https://3ds.guide then your system isn't homebrewed.

How do I know if my system is homebrewed?
Luckily, there is an easy way to determine whether or not a system is homebrewed. On the main page of System Settings, your firmware version should be shown in the bottom right corner of the top screen. Preceding it is text that should normally say "Ver." However, if your system is homebrewed, the version number will either be absent, or, if it is present, the text "Ver." will be replaced by the text "Sys".

What about old vs. new 3DS or cartridge vs. digital?
Surprisingly, there are no load differences between systems other than between homebrewed systems and non-homebrewed systems, and between different homebrewed systems. Loads of tests (pun intended) have been done on original 3DS vs. new3DS systems, and cartridge vs. digital releases of the game, none of which have shown any difference in load times.

My 3DS is homebrewed; how do I modify my times for the leaderboards?
Since the lost time due to loads is consistent, you can subtract a set time from your original time based on the category. Note that this assumes your run was deathless. If your run did have deaths, it's best to provide a video to be analyzed so the proper amount of time can be subtracted.
For Any%, subtract 13.050 seconds (4.850 on new3DS) from your time.
For Low%, subtract 13.050 seconds (4.850 on new3DS) from your time.
For Warpless, subtract 24.367 seconds (8.650 on new3DS) from your time.
For No Secret Exits, subtract 29.800 seconds (11.183 on new3DS) from your time.
For All Castles, subtract 40.267 seconds (13.667 on new3DS) from your time.
More categories will be added to this list as I calculate how much time they lose.

*More investigation is needed as some homebrewed systems seemingly lose no time to loads. This could be due to one or more of three things: The lost load times only occur on the digital version of the game, the lost load times only occur on original 3DS family systems (3DS, 3DSXL, 2DS), and/or NTR CFW overclocks the new3DS systems just enough to make up for the lost load times. For now, make sure to provide a video if you system is homebrewed, so I can thoroughly analyze it, and determine case by case whether load times are lost. Doing this will also help add to my study and help determine exactly under what circumstances load times are lost.