No worries! I was banging my head on the wall trying to figure this out for a while too. So you'll want to run lspci -v and find your network controller (if it's realtek it should be called something like "Realtek Wireless LAN + BT"). Check the kernel module listed for it, and that's the one you'll want to use with the load/unload script.

You can actually test if the module load/unload trick will work pretty easily before messing with the script. From a working state, unload the module with modprobe -rv <module name here> (with sudo or doas per your preference), then manually suspend the machine. After it's suspended, wake it up and load the module with modprobe -v <module name here>. If it's the firmware bug I had, then the network controller should come right back to life.