updates in EPEL have to spend a certain amount of time in updates-testing before they are released to stable...or enough people give it positive karma.
That's done to help in QA. As an EPEL user you could help by giving it some positive karma in the update system
But I understand the gist of what you are saying. I'll try to state it more exactly.
Because RHEL and EPEL are distinct repositories they have distinct management policies. EPEL tries to provide as coherent an update policy as can be expected given that RHEL's build system is distinct from EPEL's.
Currently there's no way to do a coordinated push, EPEL doesn't get access to RHEL update packages any earlier than RHEL users do. So as a result there will be a lag in EPEL update availability.
Can the volunteer, community run, EPEL do better at serving RHEL customers? I'd like to hear some suggestions on that. For package coordination, its difficult for me to see how. Unless Red Hat is willing to work with us to do coordinated builds prior to RHEL updates going out to the public, the lag will remain.
As an EPEL maintainer, I'd certainly appreciate if customers would let Red Hat know they'd like to see better coordination in updates between RHEL and EPEL. I'd love to see a public discussion between Red Hat, RHEL customers, and EPEL contributors on where the low hanging fruit is.