Even if they had made the change, it's still not good enough. It's very band-aid to start but worse is that it has no way to know if the policies would even target the user anyway. The idea that EXO is sending that many requests to MS Graph for this kind of thing is a little crazy. They mustn't have any MS Graph throttling to worry about, and that likely spills over causing additional throttling for regular customers using MS Graph.
It's just a bad solution all around. I wouldn't be surprised if these points I'm mentioning have at least some part in the reason for the postponement.
EDIT: I shouldn't just gripe and give no suggestions. It's definitely a difficult situation I'm sure. But I think device access rules should just be left as they are, and customers need to know not to make conflicting settings between CA policies and device access rules. I also think ALL get-AvtiveSync*** cmdlets should have gotten new replacements, not just some. It reveals the tendency to only get things half done. Its been long enough now that that initiative should have been finished off.