Here's the preset. Curious if you have any feedback.
your preset is already at 90%, basically "the" limit. (for those who don't know, the remaining 10% or so is everything else - the LCD screen, reaction to knobs, etc.)
i'm surprised the Reverb doesn't disable when you start playing, as the CPU increases about 1-3% when it's actually processing the audio.
i can confirm that turning the Trem on in this particular preset will make the Reverb disable. the preset increases CPU about 1.5 when the Trem block is engaged. perhaps this is not intended, or a bug, but with your window so small (already at 90%), there isn't much wiggle room at all.
i changed the Reverb Echo Density from 4 to 2 and i was able to keep the Reverb block on when turning the Trem on.
i'll ask about the Trem block, but maybe that's just how the trem block works. but to be honest, this is just a "too much stuff" situation with the AX8. maybe it seems like not a lot of blocks, but we can only do what the CPU allows.
setting the Comp block to a Pedal type will save about 3-4% more CPU, just an FYI - i know Studio mode is radically different.
but even if the Trem did not push it over the edge on engage, a preset already at 90% is not the best situation. if a new amazing feature was added that used just 1% more CPU in the background, your preset may not work.
so yeah, try reducing Echo Density to 2 from 4 and you could also change the Comp from Studio to Pedal. Reverb, Comp and Drive are the heaviest CPU blocks, and they're all here
when i put a Trem block in an empty preset, there is still the 1.5% CPU difference when Engaged vs Bypassed. so the behavior is consistent, and again, might be by design.