Dolphin - Metroid Prime framelimit shit comment (Issue 5982)

FYI, on my slow-as-fuck MacBook Air (where even the menu screen runs at 40-60 fps) I've always had the GC version of Metroid Prime 2 show a VPS of 60 and a speed of 100% with a lower FPS. Using Accurate VBeam, audio framelimiter + Limit by FPS and OpenAL (which has more accurate audio timing) behaves similarly to turning the framelimiter off, and mixes combinations of those options and the defaults (non-accurate VBeam, auto framelimiter, no Limit by FPS, CoreAudio) have confused me enough that I forget which results go with which options, but:
-Generally, the DSP thread always runs at normal GameCube speed. Audio never chops or speeds up. (I'm using the current AX HLE in master, not LLE or the mildly-improved new-ax-hle that optionally uses part of a DSP dump.)
-The CPU thread always runs at either 100% (on Auto framelimit) or as fast as it can run without framelimit, but it seems to lower to the GPU thread's speed if it gets to 30 fps or higher in-game.
-The GPU thread never runs at full speed and is the only thread that seems to be affected any by the limits of this poor laptop's CPU/GPU (1.7 GHz i5-2557M, HD 3000).
-Disabling Idle Skipping seems to improve performance in-game (while slowing down the main menu a bit), while Accurate Vbeam gets rid of a graphical glitch I get when the game first starts rendering on OS X (that I don't seem to get on Linux) but slows down the game in certain spots.
-Auto framelimit limits the CPU thread to 100%. Audio framelimit makes it higher.
All this testing was done in a small area of Dark Torvus Bog (in/near the save room before Boost Guardian), and involved generally staring at certain walls to see how high the framerate would go. Highest constant framerate I saw was 43, lowest was 13.