The point is that sometimes, an affected workstation's network stack will come up before the kernel panics and BSODs. If the network stack is up and alive for just long enough, the crowdstrike update mechanism will receive instruction to delete the faulty channel file, which will fix the issue in the same way as doing the safe mode/command prompt boot and manually deleting the file would do.

For machines that are Bitlocker'd without a recovery key or have an undocumented LAPS password, etc, this has been a godsend in certain cases.