You seem to be labeling overworking as "good" and in-time as "bad"... Here's an alternative perspective - I've seen underperformers who try to make it up by staying late and even allocating weekends for their employers, on the other hand, I've seen brilliant engineers who do the job and leave the office at 5PM, spending personal time on recreation, including learning other tech/stuff not relevant to their employers...
If I gave that impression I apologize it was not my intent. I don't attach any judgement to either hours invested or method of code construction. I was just sharing my observation that it is a multi-variable spectrum. That leads directly to your exact observation. Very little correlation between hours spent 'at work' and the quality of code produced.
When I started managing programmers I realized the best thing I could do was to manage people by agreed upon deliverables for their capabilities, quality, and maintainability. And if it took them 10 hrs to do it or 70hrs didn't matter. As long as I understood, and they understood, how long it would take them to do something we could manage to that schedule.
I don't think so, since the examples mention overworking towards the current assignment. Anyway, 5PM stigma exist and there is no harm to reiterate this topic.
