No impact at all. There is still a so-called graduation process in place (even if that process is way broken and changes are in progress).
This was a simple quick-fix for sites that were so obviously NOT "in beta testing", we could do something RIGHT NOW with little risk of waiting to solve all the problems with that process.
The overwrought graduation workflow has not worked for a very long time. So instead of just sitting on our bums doing nothing until "all the stuff can be fixed", we took a small, incremental step to do the right thing, even if it couldn't help everybody.
I wouldn't get too wrapped up (yet) in what this means to sites not in that list. The goal of the new process is to simplify everything for everyone so the site lifecycle becomes simple, transparent, and understandable without having to wade through endless meta posts to figure out why you haven't moved on — but most of all, the goal is to build something sustainable so sites aren't perpetually waiting in unmovable cues and needlessly entangled in dependencies and process keeping them from getting the features they need to operate.
I am trying desperately to make that process as simple as possible so we don't end up just shuffling things around into different labels doing more of the same wrapping everything around contingencies and exceptions, waiting for limited resources over which we have no control, and waiting on the Community Team to stand judge over who gets what and when stuff should get done. We've been down that road before. Let's not perpetuate that process.