Hmm. I believe this is a perfect candidate for a launcher flag!! If it could be implemented, ofc. Then, you have it off by default, and the few that like it can turn it on (and off) at will.
No, it's just a perfect candidate for responsible FREDding. All these little effects that seem like 'personal taste' can easily be used to add variety to missions, as long as they're used properly. Like if you wanted to use a warp-in for the first level of a campaign, or only for a mission that takes place immediately after a red-alert style subspace mission, I'm sure it wouldn't piss anybody off too much. And it would be much more interesting than a launcher flag, which would become worthless after the 50th time it happened.
Sorry, more often than not Launcher flags seem to be a quick and dirty solution because either some coder (

) or some group of modders don't feel like putting a little creativity into figuring out how they could use a feature in another way.
For example, I put in the -nomotiondebris Launcher flag because I thought the debris looked crappy and very deliberate. But imagine if you wanted to make a level that took place between galaxies, or in a junk field - you could very easily and very subtly dictate the overall feel of those missions by varying the amount of motion debris.
Now granted, I'm still glad that the flag is there - because it really sucks when you're trying to take screenshots and this massive pixellated rock obscures a one-in-a-million shot of an HTL ship.
But I don't see that as being a problem here...