That sounds nice, but it looks a lot like a "what if" scenario. What if I need to support a dozen systems? What if I need to do fancy 3D graphics? What if I need to do some other thing that isn't my problem right now (and likely ever)?
It's like when a web developer starts talking about how they will handle the c10K problem, or how their todo app is deployed on a fancy kubernetes cluster across the planet running on edge networks and fault tolerant, but they have zero users and no good ideas.
Just make the game you want to make. If it's fun and people love it, build it out more. Rewrite it if you have to. Hell, Minecraft was wrote in Java, then C++. Just make a game.
I think, at the very least, it makes sense to want to support Windows, Mac, and Linux. Trying to support consoles adds a massive layer of complexity regarding their stores.
"Just make a game" is fine if your game is going to be simple and can be done in a month, but there are plenty of indie games that have had only one or two developers for a couple years before even entering Early Access. A game with that kind of complexity helps a LOT to use an engine.
It's like when a web developer starts talking about how they will handle the c10K problem, or how their todo app is deployed on a fancy kubernetes cluster across the planet running on edge networks and fault tolerant, but they have zero users and no good ideas.
Just make the game you want to make. If it's fun and people love it, build it out more. Rewrite it if you have to. Hell, Minecraft was wrote in Java, then C++. Just make a game.