BYOND needs to be an Engine.
if you want to make a game using the BYOND engine that has no ties to BYOND at all, you'd need to only be able to distribute it with an equivalent of BYONDexe, and your access to hub services would have to be limited; all the hub-related procs and vars, e.g. world.SetScores(), client.IsSubscribed(), etc., would have to be disabled. Ideally, this would just be a simple compiler flag.
client/authenticate = 0world/hub = nullworld/visibility = 0
I don't think it makes sense to prevent any sort of game from becoming standalone.
releasing a free version of BYONDexe
I don't know that it's legal to actually repackage part of BYOND and release it with your game. At the very least it might be in violation of BYOND's EULA.
Nobody considers going standalone because Dream Maker doesn't provide a built-in method for doing so.
I think the majority of those flaws were in the fact that the libraries didn't play well with outside code.
Most people with a job, kids, etc do not have time to do that kind of research.
A built-in standalone build system would be just as convenient for developers with legitimate projects. The point you are trying to make there is null.
If you or anyone are going to complain about fan-games (this post was more AGAINST them than for them) yet nothing is done about them, then you sound annoying and your words have no meaning. I could've came out here and made the title "How to stop fan-games" but no, I gave "hints" in my first post without saying it. If you want changes, it starts with the man in the mirror. (or in this case, BYOND as a whole)
What's difficult for new programmers is the concepts behind them. What do I mean? Most people who come here only study BYOND. They don't go out and explore more programming techniques because they're new and don't want to be overloaded with knowledge to the point of stress.