You keep repeating this, but battery replacements were a thing before this whole debacle. I got them a few times, I think they were like $79 (yes definitely more money than the sus extended batteries I'd buy off eBay for my HTC Evo). I realize society collectively forgot about them once the back stopped coming off the phone, but surely a tech savvy hackernews would realize that they couldn't use the same battery forever without replacement.
I don't blame the guy for recommending a new phone, after all apparently Apple didn't inform all their stores about the change, so they probably had no idea that the fix was a cheap battery replacement.
They knew that old devices (especially common with the well-selling iPhone 6) would fail at peak demand, and wanted to address that, but they probably didn't have an accurate figure of exactly how many devices would be covered by the feature as initially configured.
That it took them as long as it did to react to the resulting situation is unfortunate, but could probably be explained by corporate culture at Apple, they don't generally like to admit mistakes (see the Trash Can Mac Pro press meeting a few years back).
In the end it was just a huge PR fuckup, if they had properly considered how many devices would be affected they would have realised they needed to communicate more clearly, they could have avoided lawsuits and honestly if they had played their cards right from the get go they would probably have received praise instead of backlash, but instead here we are 7 years later still explaining how battery chemistry affects integrated circuits on technical forums.
What do you do now? Your phone is laggy and there's no setting to disable the feature or a way to revert to an old iOS version. You go to the store and they don't tell you anything about a battery replacement, but instead suggest a new iPhone!
The feature was useful, the implementation wasn't. The issues weren't caused by the user not reading the changelog.