This is why specifications are important, and why design is important.
The reality is that we have certain conventions that are immediately understandable, and that too much visual complexity results in confusion rather than clarity.
If the sky is hazy white when I expect it to be blue, I'm confused as to whether it's the sky or if the map is still loading. It's adding cognitive complexity for no reason. Stars similarly serve no functional purpose at night.
What you built sounds great for an actual planetary view like Google Earth. And it sounds fun to build. But it's an anti-feature for a navigation view. When you're navigating, simplicity and clarity are paramount. Not realism.
Also, any fanciness you add in your product is something you need to then maintain. Even after the developer that built it leaves the company.
Oh come now. You are being no fun.
> This is why specifications are important, and why design is important.
Also the phrase "know your audience". No sense in casting pearls before the swine.