Alright, ive got some theories.
It worked, then didnt after you booted back into linux from windows.
You did not enable the headphones but you did have the USB plugged in.
Jan 08 18:13:09 nixos kernel: usb 1-5.3: 2:1: cannot get freq at ep 0x2
Jan 08 18:13:09 nixos kernel: usb 1-5.3: 3:1: cannot get freq at ep 0x82
Jan 08 18:13:09 nixos kernel: usb 1-5.3: Warning! Unlikely big volume range (=4608), cval->res is probably wrong.
Jan 08 18:13:09 nixos kernel: usb 1-5.3: [2] FU [Mic Capture Volume] ch = 1, val = -4608/0/1
This along with some other lines:
Jan 08 18:13:18 nixos kernel: usb 1-5.3: 3:1: cannot get freq at ep 0x82
Jan 08 18:13:18 nixos kernel: usb 1-5.3: Not enough bandwidth for new device state.
Jan 08 18:13:18 nixos kernel: usb 1-5.3: Not enough bandwidth for altsetting 1
is telling me that the USB device itself, (not the headset) may have had a modeset forced on it but since the headphones werent on, it didnt properly propagate to the headset while on windows.
Then you booted back into linux where the new mode was trying to get set and the USB device is now considered uncompliant.
First, try simply plugging the USB into a different slot, try a few slots actually and see if this shakes it out of the mode its stuck in.
Second, boot into windows, and set the mode by using them in discord or something, then rebooting (headphones still on) back into linux.
Let me know how it goes, and get snaps of your dmesg logs and journal before and after you move the USB device from one plug to another and dump the output to pastebin so i can examine in closer detail what the system is doing when its plugged into a new port. I dont need all the lines this time, just the lines immediately before and after moving the plugs.