Depends on your product strategy. If you only care about how your model will be used in the context of a harness (perhaps, specifically the harness that you designed), then the incentive is plainly there to optimize the weights within the context of the harness.
What is being absorbed into weights is tool usage. It is incredibly counterproductive to train models on a specific harness, when instead it can be trained to reason about the tools that it has available to itself and how to best use those tools to accomplish it's goal.
Would you rather hire an engineer that can adopt to your org's prefered tooling, or hire an engineer that can only perform well with their own favorite tools? It's the same thing.
I was saying more the custom skills and extensions that make the harness not a commodity. Yes people will use Claude Code, Codex, or Pi but their customizations will make their harness unique and more powerful.
Don't get ahead of yourself. Harnesses are not exactly rocket science and will be a commodity.
The real value providers here are the hardware, then the LLM as a distant second, and at a much larger distance the harness.