Native Windows support would conflict with the WSL2 stack, at its integration level. File system drivers aren't generally designed to share the underlying block

Native Windows support would conflict with the WSL2 stack, at its integration level. File system drivers aren't generally designed to share the underlying block device between different kernels concurrently. The block device isn't consistent with the latest writes without flushing caches, and a native driver wouldn't see those caches without hooking the Linux kernel, but that's not the WSL2 integration point. WSL2 is based on virtualization not kernel hooking. Native Windows would be able to access the file system as long as you killed all WSL2 processes first, and vice versa: run any WSL2 process and lose native access. Access via network makes far more sense.