Quit crying, do your job and a little more, then you shouldn't have any worries
Some teams, that have been stable for 5+ yrs have already weeded out the bottom 5%, or even the bottom 10%. Sure, there may be one or two people on the team that are not performing at the level of the top person, but their least performing person could be someone who's beating expectations and going above and beyond every day and is far better than 80% of other teams "meets expectations. Do we really want to get rid of them?
Let's say you do get rid of this person who does their job, and a little more, but it's not as much as the rest of the team, so they're the bottom 5%. Now you hire someone who doesn't work hard, doesn't do a little extra, and you have to get rid of them. And so on and so on. Now you have a sacrificial lamb to cut every LR, but once everyone knows "da new guy" is a sacrificial lamb, da new guy will figure it out and quit or just slack off and do nothing until the next LR and the team will be stuck carrying the workload that the original above average performer who had to be rated as bottom 5% was doing while da new guy doesn't do squat.
This is a stupid policy. I have no issues with ranking people because there will always be best, average, and least performing people, but only those who don't meet expectations should be ranked as needs improvement and marked for possible PIP or LR.
Then there's the teams, non-sales, where some people get to work on initiatives, special projects, new features, whatever, that get high visibility while others on the team handle cases, run-the-business, fix bugs, etc. and get very little visibility. When ranking time comes, those people who worked on the high-vis projects get the top rankings while the rest get lower rankings. But you get rid of the run-the-business folks, then you have to make your project people waste time getting replacement new hires up to speed or do the mundane work themselves and then they're not available for that high-vis work.
And, the reality is, that ranking are about visibility, internal politics, and costs. You can have a high performing person who goes way above and beyond, but if they have 10+ yrs of tenure, they're expensive compared to a new hire so they get cut to bring in someone with 5 less years of experience, who is younger, and hire them at a lower pay grade and save money. Or hire two people 2 pay grades lower to get twice the level of basic work done and hope you still have someone on the team with enough corporate history to know how things work, how systems/applications/tools were upgraded last time, and what all the dependencies are. So much stuff gets overlooked. Sure, the guy who set it up or ran the upgrade process may have documented it, but does everyone else know WHERE that documentation is? Did that person who wrote the documentation document everything or assume some key facts were just known by everyone on the team, and once they're gone and their backups have to do their work, will they remember that "obvious" thing that wasn't documented until after it bit them in the a-s?