Attempts to militarize gaming technology are uniform (ha) failures. I've been a military contractor working in communications and electronics for the last 25 years. I've watched initiative after initiative crash into the rocks. The two mindsets are completely alien to each other. Getting people who work in FAANG companies - or Microsoft to talk to actual soldiers is laughable. And smaller firms don't have the technology you are talking about, or the gravitas to get their way with the military.
I'll give a brief example. It occurred to someone that Microsoft's edge stacks - with a local implementation of Azure - would be great stuff for forward deployed units. The demand from the MSFT side (and in essence the hardware provider) was that only their staff handle basic maintenance, like replacing drives. This then breaks on the rocks of "who is going to go to Kabul or whatever other shithole we happen to be operating in to replace this hardware". Then, the military's clear reluctance to be dependent on a commercial entity for the actual logistics of fighting a war. They'll hire consultants to consult and train their people, but not to be dependent upon, even though an honest conversation with officers will result in them admitting they _are_ utterly dependent on the external support. They have to pretend otherwise for leadership consumption.
Another example is the Google rebellion over sharing AI with the DoD. Are they really going to get in bed with organizations that would do that with them? Fuck no.
Lastly, the people that work in those companies have no relationship to military imperatives of mission, 24x7 operations regardless of circumstance, that kind of thing. Two different languages. The problem has gotten _worse_ rather than better over time. Embedding say, MSFT people in with a unit does bridge the gap a little, but only a little.