Developers always have to power to just not implement the feature.
If you choose to work on such features, remember it's a choice you have made. You may come to the conclusion that your personal gains outweigh the damage you create to other people but it's still your responsibility. You can't delegate that away to sleep better at night.
The feature will get assigned to someone else, be implemented and you will be fined in performance review if not outright fired for not doing your job.
If you do other things on that project making it better, you're still complicit.
Your only bet is switching projects if you want to stay at the company, which would be harder most of the time. (Because sociopaths rule.)
There are more effective ways to fight it, they're not by refusing orders. You're not deciding someone's life here nor playing God and decisions get reversed with damage being mitigated if any.
So the argument has now shifted from "managers are forcing it on innocent developers" to "devs with no conscience are going it to develop anyway so who cares if I am to one doing the work?". This is important to recognise. There have to be developers willing to implement those features in the end. Without them every would fall into crumbles. Why does nobody feel the shame being one of them?
I'm not seeing any of that. Just shrugs at being a mere pawn in a large game and trying to gain as much personal benefit out of it as possible.
If you choose to work on such features, remember it's a choice you have made. You may come to the conclusion that your personal gains outweigh the damage you create to other people but it's still your responsibility. You can't delegate that away to sleep better at night.