Issue With IR Pointer Lag

[turbosheep]

ISSUE
While playing Metroid Prime 3: Corruption, the IR Pointer aiming reticule begins to lag over time.
It starts out very smooth, but becomes increasingly worse (very jerky/laggy).
Lag also present in the game's menus; the jerkiness even remains in the Wiimote menu (home button).

I'm playing with an original Wiimote using Bluetooth Passthrough and a supported BT adapter (Orico BTA-403).
Brand of the USB Sensor Bar is 'Cablebee'.

Everything has been working great in other games I've played (Twilight Princess, Wii Play, Super Paper Mario).
Although MP3 is the first game I've played to constantly use IR aiming, I've never noticed the fairy in Twilight Princess to move in a jerky way like this.

WHAT DOES WORK
-Disconnecting the Wiimote through the Wiimote menu (home button) and reconnecting (pressing '1' and '2' buttons) DOES work, but only for a minute or two.
Then the lag returns. A very short-term solution.

WHAT DOESN'T WORK
-Distance/lighting regarding the sensor bar doesn't seem to do anything.
-Performance and/or state of the game doesn't seem to matter; running at stable 60FPS.
-V-sync on/off, resolution, different backends, Asynchronous Ubershaders on/off... no dice.

[JMC47]

Either the USB sensor or the bluetooth may be overheating and causing connectivity issues.

[turbosheep]

After playing for about an hour and a half, I can confirm the issue is entirely gone when playing without Bluetooth Passthrough.
Emulating the Wii's Bluetooth adapter prevents any IR pointer lag occurring in Metroid Prime 3: Corruption.

I also played Mario Galaxy for about an hour, with Bluetooth Passthrough, picking up as many Star Bits as I could (requires IR pointer): no lag whatsoever.
In other words, Bluetooth Passthrough works perfectly fine for me in every game I've played so far except for Metroid Prime 3.
Unless Metroid Prime 3 can cause USB BT adapter or Sensor Bar overheating, I'm pretty sure we can rule that out.

Though I have a solution now, I'm still very curious what the issue could be.
It seems to be software-specific (Metroid Prime 3), but exactly how that'd be possible is a mystery to me.