Repeated crash: panic(cpu 2 caller 0xffffff8000e459fa): Kernel trap at 0xffffff8000b980a7,

Kernel Panics can be caused by either hardware or software. Unfortunately a single Kernel Panic report is not enough to determine the cause. See if you have any more Kernel Panic logs that you can post which may show us a pattern in the crashes. The Kernel Panic logs should be located in "/Library/Logs/DiagnosticReports" if they exist. The files will begin with "kernel" and end in ".panic".

Run the Apple Diagnostics to see if any hardware issues are detected.

To look for possible software issues run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.

From your First Aid report:

warning: MT mapping (0x4000006fc7276 -> 0x11c1ae3, 1, C) is not completely referenced

warning: MT mapping (0x4000006fc7277 -> 0x11d2cd8, 2, C) is not completely referenced

Too many warnings of this type generated; suppressing subsequent ones.

This could possibly be causing problems. I personally would break the Fusion Drive and set up the Fusion Drive again from scratch and restoring from a backup or clone:

https://support.apple.com/en-us/HT207584

The other volumes shown on your Fusion Drive are completely normal starting with macOS 10.15 Catalina (macOS 11.1 Big Sur adds some other volumes as well):

https://support.apple.com/en-us/HT210650

Regarding your networking issue try a PRAM Reset (hold the PRAM Reset for at least three chimes so it activates several times). Unfortunately Apple likes their cryptic errors so it is hard to say the exact issue, but it does mean you have some sort of networking issue with your Mac or your network/Internet connection. It is also possible that a failing internal hard drive could slow the system down enough to cause problems booting to external media including Internet Recovery Mode.

Before you go to the trouble of re-creating your Fusion Drive I highly recommend you first verify the health of the hard drive by running DriveDx and posting the report here.

Make sure you have a good backup.

I don't see any software issues, but I am also not familiar with some of the software installed so maybe another more knowledgeable contributor will chime in if they see a problem with the software. I do see an extremely high system load which is not good, but I'm not sure of the cause. Make sure you third party apps are completely up to date.

Try booting into Safe Mode to see if the problem disappears. If the problem disappears, then one of the apps listed in this report is most likely causing the problem.

Run Disk Utility First Aid on the "Fusion Drive" or the Container (or both). If you don't see the "Fusion Drive"or Container listed in Disk Utility, then click on "View" within Disk Utility and select "Show All Devices". Even if First Aid reports everything as "Ok" click on "Show Details" and check for any unfixed errors. If you see any unfixed errors listed, then it will require erasing the whole Fusion Drive and restoring from a backup or clone. An unfixed file system error can greatly affect system performance and can even cause Kernel Panics.

Check the health of the hard drive by running DriveDx and posting the report for the hard drive here using the "Additional Text" icon which looks like a piece of paper.

If you have more Kernel Panic logs, then you should be able to open them within the Console app so that you can copy & paste the contents of the panic log into the "Additional Text" icon like you did with the EtreCheck report and your previous logs. I'm only interested in the Kernel Panic logs whose file names begin with "kernel" and end in ".panic". The "Full Problem Report" you included in your original post is the example of the Kernel Panic log I'm looking for. Unfortunately it seems none of the more recent Kernel Panics have been saved since they are not noted in the EtreCheck report.

Geir Kristoffersen wrote:

The D command and the Option D command starts software reinstall over internet.

I only get a spinning glove and a drop down box with all the networks in my vicinity.

I let it run for a while to see if it comes up with some sensible choices, but no, so I terminate the process and power up again.

If your WiFi's SSID is hidden, then you need to manually enter the SSID and password by clicking on the "...." option. You can also connect your Mini directly to your router using an Ethernet cable.