If everything worked like it was supposed to, we wouldn't be talking about bringing people completely outside the profession into the ranks as full colonels.
What you just described is the polar opposite of what I saw warrant officers in aviation, intel, SF, and maintenance fields. They were all the epitome of "hands on." There's no reason to assume that if cyber warrants were hired for those skills, they wouldn't be put to use in the force.
I agree with everything you just said. It's the cyber Warrants that I'm specifically referencing.
I think that the difference is that the military has kept up, or pioneered, in those fields you mentioned. In IT, they've outsourced so much of the function to contractors that they have lost the institutional knowledge of how IT works in the real world. Now most of them are reduced to following an installation checklist developed by civilians and, if it doesn't work, they have no clue how to troubleshoot. How many times has your laptop been reimaged when something was not functioning correctly? I know I'm painting with a broad brush here. I very much want to emphasize that it is not the fault of the individual Warrant Officer. The problem is systemic, DoD wide and starts at the various schoolhouses. Over 7 years and a couple of deployments I worked with quite a few Warrant Officers from CMF 250 and other branch equivalents. Of all the ones I worked with, I can count the ones that I would feel confident labelling as a Senior or Tech lead on my fingers. Of those, two were AD and the others were consistently reserves/National Guard (one of the AD ones I mentioned was technically sound, but would not have been able to hold a job in the civilian world because he was constantly belittling all of the enlisted around him). The ones from the reserves, with one exception, all held IT jobs in the civilian sector that directly aligned with their military position. The one exception was a Reserve Warrant Officer that also served as a contractor on the same system during the week. My point, which I discussed at length with a MACOM J6 is that, as long as the military continues to outsource all of the essential IT functions to contractors, the institutional knowledge will not be regained. Right now the only people that I would consider hiring for truly technical positions based solely on military experience are some of the Air Force folks and those only for mid-level technical positions or pure management positions.
I also think that the entire CMF 25 is suffering from the inbreeding effect. Basically, as knowledge has been passed down over time, some of it has been incorrectly understood by the student. Later that student passes down their imperfect understanding to their students, who understand it imperfectly and so on... As time passes, they are perceived to be inferior at their positions and the quick fix is to hire from outside. As a result, the students lose the ability to gain experiential learning in their field.
If that is the problem, the only solution is to bring in people from outside that have the right skill sets, the authority to impose the proper way of doing things and the ability to help the military regain their knowledge and catch up to the pace of new technology. I think it will take at least a decade for an organization like the Army to begin to internalize the skills required for enterprise level IT. It will take another decade to actually get back to the point where the military services are capable of self sustainment without the need for contract labor. So how do you do it? Exactly the way that was proposed. Bring in some of the known big guns to teach and give them, perhaps initially too much, authority that will ease the political process of effecting change. The lack of technical knowledge is a symptom of a flawed system. Effecting actual organizational change in a bureaucracy like the military, especially one as massive as the Signal Corp (and other branch equivalents) will take true leadership that cannot be effected at the Warrant Officer level due to the political pressure that will be placed on them to just "get it done". Without a true understanding of the longer term effects of their decisions, the balance between "right" and "right now" will always swing too far to the side of "right now" to actually be effective for more than the duration of an OER cycle.