As pointed out by @jkotas in the #117727 (comment) thread on PR #117727, if we bounce between running jitted/compiled code for intrinsics and interpreting them, this will produce inconsistent IsSupported/IsHardwareAccelerated return values and as a result inconsistent application behavior or crashes.
The most likely shipping configuration will be R2R + interpreter, so we need to make sure that in this configuration we R2R-compile every intrinsic that might possibly get used, so the interpreter can invoke the R2R'd code for all intrinsics where possible.