What I see on SO is a lot of really annoying people refusing to answer simple questions because they believe, based on nothing, they know more about the question than the person who asked it.
When asking "unpopular" questions on SO I usually include a disclaimer along the lines that I want to know the answer for education purposes and any answer that is not specifically addressing the question at hand will get downvoted and never accepted. This works to some extent.
In the end, I stopped asking questions on SO because dealing with this kind of behaviour was too tiresome. I'm glad to see I'm not the only one who thinks like that
Never ask them anything about Linux networking. They get so excited to gatekeep the information and tell you that you don't know enough to be safe doing whatever you're doing.
I've actually been super curious lately what happens if you route a PC's localhost to someone else's IP, but I have no clue how to ask on SO without baiting out the obvious "don't do this" and the generic "stuff won't work". Obviously, I could do it myself and explicitly see stuff not working, but I'd like to find out what actually happens under the hood and why things break; SO seems like an awful place for these kinds of "what if" questions and I don't know a better place to ask.
You're curious what happens if you add a route for 127/8 to somewhere other than the loopback interface? Or do you mean making it so that the hostname "localhost" resolves to something other than 127.0.0.1? Give it a try.
Also the case where for the original asker it really was was an XY instance, but now the top google result for "how do I fill a bathtub using a hosepipe?" goes to a Stack Overflow page full of people refusing to answer the question.
The thing is, 99 times out of 100 it really is an XY problem. If you're the 1 out of 100 then it sucks to be you; I guess the free advice is worth exactly what you paid for it.
I don't often make that accusation, but the last time I did that's exactly what it turned out to be. They were trying to dive deep into the internals of C++ to find out why their debugger was hanging, and what they were asking for just didn't have an answer. They finally found that they were doing something that led to undefined behavior, and if they had asked about that instead the question would have been answered immediately.
