Hi Miga,
I don’t think it’s directly an ACES OCIO issue, but rather an implementation issue. We can achieve inverse display transforms via the use of OCIODisplay which AE unfortunately didn’t implement yet prior to release. I believe OCIOv2 is designed to be set up in the way ACES has implemented it, with displays being separated from color spaces so the Studio and CG config are pretty much what they should be.
Your point was also brought up recently in this thread where I mentioned that it could help to give Adobe some feedback on this to make them more aware of how much of an issue this really is.
Are you sure that this is caused by OCIO? AFAIK there is a misinterpretation happening with ARRI .mxf files (ProRes) on a Mac in Adobe Premiere and After Effects likely due to the encoded matrix coefficients being bt.601 instead of bt.709 but it’s always assuming the latter. This issue isn’t seen on Windows. (Or it was the other way around).