FPS drops to a weird cap of 23 FPS, sometimes 45 FPS

My usual FPS is around 140 in the menus and around 80-90 in a match.

Sometimes, however, I will drop to a weird spot of around 23 FPS (it can also be around 45-47 FPS). This is usually triggered by Alt+Tab-ing or just interacting with /clicking on anything that is not the client (say, Discord). It can also happen when going through the in game menus very quickly. This does not happen in any other game and is independent of my CPU and GPU thermals.

I can usually hot-fix it in a few ways. First one is just changing anything in the graphics settings (ex: rendering scale). The second one is pressing Ctrl+Alt+Delete and going back to the game. Third one is using the Ctrl+Shift+Windows+B keybind. All of these seem to snap the game back out of this weird FPS cap and the game starts running smoothly. Although, this is only a temporary fix as the more game is open the more frequent these FPS drops seem to be (these solutions also then stop working after a while). When this bug is affecting me, these FPS drops usually happen 1-2 times a match, and if I play a few more matches they can be as frequent as 5-10 times, or even near constant.

Weirdly enough, whenever the game is stuck at those 23 FPS, Alt+Tab-ing or just having another application in the foreground brings the games frames UP to 30 FPS. Going back to the game then drops the FPS to 23.

I first started having this issue in the middle of Season 1, which lasted for about two weeks and then went away. Then this issue appeared back in the first week of Season 2, disappeared after the next patch, and then reappeared again after the patch this Tuesday.

Specs: GA402RK laptop with RX6800S and Ryzen 9 6900HS. Can be playing with platform power limits anywhere between 70 - 125W, but usually around 115W.

Here is a video of this happening: https://youtu.be/xyXpcYNkWGQ
At 0:28 and 1:30 I do the Ctrl+Alt+Delete trick to fix the frame rate.
Here is DxDiag of my system: https://pastebin.com/kj40raVF

All graphics and chipset drivers are up to date (the one in the video and DxDiag were the latest at the time of the recording. After this bug reappeared this Tuesday I updated Adrenalin Software to the latest patch, the bug still persists. Resetting the shader caches through AMD software did not help either).