So first of all, it would be nice if this hypothetical "better" algorithm already existed, before we start limiting votes here & now, on this instance? Don't let perfect become the enemy of good?
Second, I think you've missed something wherein while each vote is individually binary, in aggregation they become a numerical value that is no longer binary - something that receives 1000 upvotes is significantly more popular than something that receives only 10.
Third, whether the current system is "good" or not is not something for us to judge? If people WANT something, then why prevent them from having it? Even if something else is "better"?
Sometimes people browse by New, and these people will not be impacted (on the side of receiving fewer votes than before this anti-feature was implemented), however many people desire instead to spend their time differently, and be alerted to what others have found to be "good". This is obviously not a perfect metric for what YOU may enjoy, but... it's a start?
We don't need to engage in binary thinking ourselves: a system can be more than simply "good, so keep it as-is" vs. "bad, so now get rid of it entirely or at least start limiting it", there are shades and nuances possible within all of this. Especially the knock-on effects, I mean events that transpire downstream and as a direct consequence of the upstream ones, even if logically they seem at first to be disconnected. e.g., what link is there between offering posts vs. votes - none? But if people leave an instance as a result of this change, then fewer post content can result, despite the seemingly disconnected nature of those two.
Voting makes the Threadiverse "welcoming". You call it dopamine but however it is implemented, it makes people feel good to be here, and to contribute to a community. Perhaps even a wider, global community, beyond what they could reach if they merely went outside to touch grass irl?
So yeah, make that better system first, and then offer it to people as an opt-in feature. However, the point of this post was to discuss a mandatory new feature that removes existing capabilities, NOW not at some future date when your mentioned hypothetical opt-in feature has been deployed to a production environment where people can use it here on PieFed. So you might want to put your comment here over into the original post discussing this new voting feature? Because it does not seem terribly relevant to me for it to be HERE, discussing just how mandatory this new feature should be made as? ... unless you truly do want the capabilities of others to be curtailed?