The Hacker Ethic is not a set of guiding principles designed or built to promote the adaptation of programmers to development processes and business planning. And it shouldn't have to be.
Very well, you may want to train people within a different mindset prepared to fit into a process, acknowledge the existing rulebook and basically play nicely by it, working with others in developing business-oriented code for business purposes. But the Hacker Ethic is much more a cultural development for what was at its time mostly a subculture, than it is a series of well-defined principles for development. The Hacker Ethic emphasizes a series of value and skills that are perhaps way beyond a business development context - in that they belong much more in the future than they belong in the well-defined production/industrial contexts that we have come to tbe acquainted with.
So to put forth such an argument, that the Hacker Ethic harms developers' possibilities of conforming to market standards, is just that. It means conforming, thinking inside the box, and so on. Such is not the Hacker Ethic, and is not meant to be, and doesn't have to be. Just because there may be other, different objectives than those embodied in the HE, does not mean it needs to be put aside, transformed, or somehow modified. It's just different contexts.