Device shows up on client, but stops working after attached

[SK-Infidel]

Setup details:
Windows 11
WSL2
Custom kernel and headers with cfg80211, usb wireless and all needed usb tools running builtin, not as modules
win usbip on host
aircrack-ng 88XXau driver installed
kali large with wifi features installed

My procedure:
On host:
usbipd wsl attach --busid x-x

OR

on kali
usbip attach -r=hostip

Behavior:
When I plugin the adapter you can see the device initialize and it's led begins flashing
attaching the device causes the led to stop flashing and remain stopped as if the device is locked up, or has gone into some kind of lmbo in which it's connected but not initialized..

if I run lsusb on the wsl distro the device is listed, yet the drivers don't seem to see it and create a new interface.

lsusb output:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg shows that it connects ok:
[ 807.453758] usb 1-1: new high-speed USB device number 2 using vhci_hcd
[ 807.653768] usb 1-1: SetAddress Request (2) to port 0
[ 807.710749] usb 1-1: New USB device found, idVendor=2357, idProduct=0115, bcdDevice= 2.10
[ 807.712825] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 807.713537] usb 1-1: Product: 802.11ac NIC
[ 807.714273] usb 1-1: Manufacturer: Realtek
[ 807.715127] usb 1-1: SerialNumber: 123456 (super unique serial number, lol)

cfg80211 is builtin, so it doesn't show in lsmod, but the device driver is loaded..
Module Size Used by
88XXau 2379776 0 <-- but not used by anything..

I'm running the most recent version of usbipd win.

I've checked to see if usbip traffic is excepted in the windows firewall and it is, and just for troubleshooting I completely disabled it.. No change.

Attached is a copy of my kernel config.
KernelConfig.txt

and to show I'm booted into my custom kernel which supports all this
uname -r outputs:
5.15.123.1-microsoft-standard-WSL2+

Not sure if I'm doing something wrong with my kernel config or if your software is not working as expected.

[SK-Infidel]

Turns out the device chipset was being misreported and a different drive works. Your software is working as designed. Disregard