I usually put scare quotes around it “correct”. Which means attemting to deliver something as close to the scene as possible. Using tools and settings following best practice to achieve that and finally making careful subjective judgements with this goal.
But his assumes that a good default is about getting a pretty image regardless of what was captured. That’s quite the assumption. Lots of tools attempt to smoothen mistakes/gear limitations but how much of that to apply must be the result of discussions taking other parameters such as transparency in mind.
Current defaults exist. There is no difference. A better overview of why defaults look like they do coupled to an idea about workflow and usability brings clarity.