It seems to me that if you want to convey that you disagree with those people or their assumptions, using their snowclone to describe a tool that actually solves a problem that arose recently is counterproductive. If I wanted to convey disagreement, I might release a tool called, say, "Make HN Readable Again" that added a bunch of slow JavaScript and popups. (And if I wanted to convey neither agreement or disagreement, I'd pick a different name.)
All effective communication is "censoring yourself". When I say that I'm a software engineer, I'm refusing to say that I'm a kazoo player, because I intend to convey the idea that people get when they hear "I'm a software engineer" and not the idea that people get when they hear "I'm a kazoo player." No matter how much I dislike (or like) kazoo players, I'm not going to attempt to reclaim the term from them.
And the English language is descriptive, not prescriptive. When a phrase has a well-established meaning - whether that meaning was first by commoners 400 years ago, or commoners today, or (for some languages) a bunch of academics in an ivory tower today - people are going to think I mean that meaning when I use the phrase. If I want my communication to be effective, it's on me to pick words that I expect people will understand, not on my audience to figure out what I really meant.
When I communicate, I intend to communicate the most accurate thing I can to, yes, the broadest audience I can.