By the way, I understand this is a fundamental aspect of how Lakeflow Jobs and Tasks has been designed. 

I'm just trying to find a significant reason, that justify the design pattern, as this can not be the only reason to allow establishing sensible defaults at the job level while maintaining the flexibility to customize individual tasks when needed.

Actually, wouldn't maintaining the inheritance and restricted scope precedence, give a much better flexibility instead?