Bell Labs tried to kill their child and supplant it with plan-9 and inferno.
It failed.
Not because they were bad OSs, but because once you have market domination and code, things _must_ be backwards compatible.
If Linux/GNU didn't imitate POSIX, it wouldn't be any more popular than Haiku.
POSIX is clearly a standard for C unixes, but you could imagine a restricted subset of POSIX that didn't govern libc being applicable to a non-C Unix.
Any operating system written in a non-C language with no C support is going to break all existing C applications. This is inherent to OP's desire to remove all C. For the record: I'm opposed to removing all C.
So why not preserve unix-like shells, filesystems, devices, commands, etc? None of those are tied to language of implementation. Potentially existing unix shell scripts could run safely on a purely non-C system. Sysadmins would carry over some familiarity from existing Unix-alike systems. That has some value.
Unix servers make up 68-98% of the internet, depending on who is measuring. There's a huge body of sysadmins familiar with shell who are not familiar with Powershell.
So that's exactly my point: I don't think we should start from scratch on things like the Unix shell, filesystem hierarchy, devices, etc. People know them. Throwing out systems people already understand for no reason is a huge anti-pattern.
If you think Powershell is superior, port it to Unix and convince Unix sysadmins to use it. I don't think it's going to be very popular.
Once you've learned how it works having an object oriented shell is game changing. Powershell isn't necessarily the ideal implementation but I'm just calling attention to it as an existing, popular example of something better
So until we get to replace POSIX across the board, C will be around.
It will take generations.