Interesting report, I am glad I didn't move to 2024 yet. I am really looking towards color management, but if this is the current state between Max CC and Corona.. that's not good.
Hopefully this can help with more research and fixing by team.
2James: Max 2024 CC (to manage input/output, effectively just adds CC on top of basic Gamma 2.2. only), Corona's internal rendering Color Space (hidden within Devel/Debug settings) and ACES OT tonemapper are 3 completely unrelated things right now. They don't relate, or connect in any way. The ACES OT has nothing to even do with ACES color pipeline, it's just unrelated tonemapper.
And every possible combination (however weird, like sRGB input, AdobeRGB rendering space, ACEScg Output, etc..) should nonetheless produce fully stable, always identical result.
Corona has also never been rendering anything in basic sRGB (Vray was though, since Vlado had some strange argument with it..), it had this weird generic "WideGamut" color-space, which can now in DevelDebug change to either more industry-common standard AdobeRGB or ACEScg, neither will produce much different outputs. It's just different arbitrary limit to what space the calculations will run in.
Max 2024 CC will be most beneficial for correctly displaying colors on high-end displays, like in DCI-P3 (which all modern HDR supporting monitors offers, market-wide it defeating AdobeRGB, mainly because of Apple's support behind), offering seamless colors between Max and Photoshop (or other post-application). Right now you either downgrade your monitor colors to prehistoric sRGB, or Max will show wildly different colors than CC-managed app like Photoshop (hence 100 threads "why is my framebuffer different then image I opened in PS").