Quote from TorhalMemory isn't the issue. It's CPU cycles, which directly affects your FPS.
Clearly for quite a number of people, CPU cycles isn't the issue. It's the lack of an adequate solution presented by the alternative.
It's fine that ora3 is technically superior. In an ideal world, my raid would run it, and I'd have extra cpu for other things, which would be nice. ora2 *is* ancient and I'm sure ora3 is better.
The goal of superior code and efficiency is that of technical people, but most regular users just want usability and functionality. This is not an isolated incident of this schism!
Still, it is not 'better' if it isn't acceptable to your userbase. To the programmers, this is progress, and users that don't get it. Personally, I'm happy to spare the time of my processor instead of my own game time, trying to push unitframe changes onto an entire raid.
For those that need to keep ora2 running, the cooldowns are in ora2_participant\Participant.lua with the Ankh cooldown on 112, and the rebirth, soulstone and DI starting at line 125. See the previous page for a fix for the readycheck issue.