It's in the spare rig with the Asrock B850M-X wifi (ver:1.0?) so it's rather gimped, but not with hidden limiters as far as I can tell.
The current limiter I mention is omnipresent, as far as I have been able to tell. ASUS is the only manufacturer I know of that provides settings to disable it (though I've mostly used ASRock, Gigabyte, and ASUS on this platform and have very little experience with AM5 MSI boards).
This limiter causes some tests to pull far less power than might be expected, throttling the CPU back before getting anywhere near any temperature or PPT/EDC/TDC limits. AVX and AVX-512 heavy apps are most commonly affected, but it's not exclusive to them. Without the limiter, it's possible to get a 9800X3D to 230W+, if not immediately thermally limited, in some scenarios.
Anyway, AIDA64 CPU/FPU/Cache test is one of those tests that seem to be heavily affected by this limiter (which doesn't really seem to make the test any easier to pass, unless one is using positive curve shaper values at medium loads.
Now that I'm back on my ASRock B650M-HDV/M.2 the CPU/FPU/Cache tests bounces around 5.05-5.2GHz at 1-1.1v and ~110W at barely over 60C on my air cooled (lid intact, CPU and cooler lapped, TR Royal Knight 120SE, DOWSIL TC-5888, etc) 9800X3D (+200MHz, 1x scalar, -27 to -40 on COs, 'motherboard' power limits). My Gigabyte boards were very similar. However, this test was like...40-100W more at times on my ASUS B850M with "Disable Current Limiter" enabled (which is a distinct and largely unrelated setting from any of the PBO limits or 'peak current control').
If your part isn't holding full boost in the AIDA test, but also isn't reaching PPT, EDC, or thermal limits, you almost certainly have this limiter (as I would expect from essentially every AM5 system that isn't using an ASUS board where it's explicitly been disabled). Other tests, even AVX-512 ones, rarely hit this limiter so hard, if at all. I'm not sure what it is about AIDA64, but the large gap I see between the highest core temp and the highest die temp suggests to me that dLDO transients, or VDDCD_VDDM (cache voltage) could be what the limiter is actually targeting.
Anyway, some examples of my current setup, where this limiter is more (AVX-512 AIDA64 CPU/FPU/Cache) and less (AVX2 LINPACK 2019) evident, but definitely present:
Again, exactly the same system configuration for both...didn't even restart between tests.