I did not say you should revert to your internal card but that you should use a usb card with a supported chipset (the modules should be the same across all arches so ignore the fact that this is armhf):
$ find /snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ -name '*usb*'
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ath/ath10k/ath10k_usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ath/ath6kl/ath6kl_usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/atmel/at76c50x-usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/intersil/p54/p54usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/marvell/libertas/usb8xxx.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/marvell/libertas_tf/libertas_tf_usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex_usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/mediatek/mt76/mt76-usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/mediatek/mt76/mt76x02-usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ralink/rt2x00/rt2500usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ralink/rt2x00/rt2x00usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/ralink/rt2x00/rt73usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/realtek/rtlwifi/rtl_usb.ko
/snap/pi-kernel/current/lib/modules/5.3.0-1028-raspi2/kernel/drivers/net/wireless/rsi/rsi_usb.ko
if you do not want to maintain your own kernel snap (in which you run the dkms build during snap creation time), the alternative would be to have a driver snap that you need to keep fully in sync with the existing kernel snap (i.e. if your kernel updates before the snap you will have no more network access) …
for both solutions you need a brand store (non-canonical kernel snaps are only allowed in brand stores, and for the second solution you need the kernel-module-control interface which is also taboo in the global store)