So, the difference between a "hacker" and an "engineer" has always been this idea that the engineer is designing something which is principled at all levels, whereas the hacker is putting together something which works in the most obvious cases but doesn't necessarily cover all of their bases. In practice, I think we all know that a little of both is best; ideally you can throw something together with copy-paste prog…
I think I agree with your overall point, but not really with this phrasing. Say you apply the hacker concept to food. You can make some cool food at home while bending the rules and everything is fine, but if you open a restaurant and make all your customers sick as a result, then you're just a bad chef.
Hackers hack hacks. Bringing a hackers mindset to something else means that you can see when a hack is appropriate, not that you "hack" things that aren't.
It's like this popular quote... "Rebels learn the rules better than the rule-makers do. Rebels learn where the holes are, where the rules can best be breached. Become an expert at the rules. Then break them with creativity and style". Not "Be lazy, claim rebel".