Answers are for all future readers looking for a solution to the same problem. When you answer, try to make it applicable to the most people possible, rather than tailoring it to the perceived knowledge of the OP. E.g., on a technical solution for an OP who is advanced, it doesn't hurt to include explanation for the novices who will read it later. It's also a good idea to include any assumptions you've made since the next reader may not recognize the limitations of the answer. Answers that teach tend to get a lot more upvotes than brief answers tailored to the OP. :-)

Also, observations like that answer, especially without authoritative citation, are more suited as a comment because they aren't a solution or definitive answer. At this point, you have lots of options. You could move it to a comment and delete the answer (and get the rep back). You could expand or change the answer to make it better. You could simply delete it. Nothing says that once you post a brilliant pearl of wisdom, and it turns out to be not a great as it seemed at the time, you have to just leave it there as-is. :-)

All my points have already been made, but about your referenced answer: you say you understand why that might be downvoted, but you don't say what that is. In general, saying something can't be done will often come back and bite you in the butt when someone else posts a "thinking outside the box" solution. For example, there are a number of editors that would allow you to embed the PDF pages on new PDF pages that have numbers. So even if you can't change the original pages, you can still achieve the result. (cont'd)

ReactOS is not beta software. It's alpha software. So it's "pre-release" in an entirely different sense and the comparisons aren't valid. But there is no point in trying to discuss this further, it wouldn't be constructive.

If it isn't technical reasons, the reasons are off-topic or out of scope. It received an answer that talked about some technical differences you weren't aware of (or at least didn't mention in the question). But that didn't actually address whether it would account for a 10x price difference (and I'm guessing not). But if you want to pursue modifying the question so it can be reopened, I'd be happy to help if I can.

Apply this to your question on the KVMs, which probably could be asked in an on-topic way (and maybe we can figure out how to reword it and get it reopened if you're still interested; it would be a substantial rewrite and it didn't seem appropriate to do that pervasive an edit). It is about classes of equipment. It had a few problems as written. It focused on cost instead of technical differences, and that is easy enough to fix. The bigger problem was that it speculated about technical reasons and ruled them all out. (cont'd)