I don't have these "freezes" on my 2018 i7 Mini, but maybe it's related to the size of the SSD and the amount of free space? I have the 2tb SSD and it is about half full. I use a new (space grey) Apple bluetooth keyboard with numeric keypad and also have a magic mouse 2 (which is connected, but I actually use a USB mouse most of the time).
I experienced these occasional freezes on the Mac Mini 2018 Mojave with 512GB SSD / 32GB RAM, which I recently sold. Since yesterday a Mac Mini 2020 Mojave with 2TB SSD / 64GB is sitting on my table, but to early to tell if the issue is still there.
According to the few sources available on Apple and SSD TRIM, trimming happens during booting and when repairing the disk with Disk Utility. But if this is or still is true is another question.
Maybe my recent installation experience might be helpful for others, and maybe there is a relation to the system freezes. My proven standard routine for efficiently downgrading and cloning to Mojave from the preinstalled Catalina was a nightmare on the new Mac Mini and took me 3 days to solve. Deleting the Catalina partition and installing the base Mojave system was involving but worked fine after reboot.
Then I rebooted the MM 2020 into Target Mode and deleted the mounted APFS base system and cloned my Mojave system and user files with CCC. My Mojave APFS partition worked perfectly on the previous Mac Mini. Upon reboot the MM 2020 got stuck at the Apple logo and I was not able to fix this. Even updated the T2 bios via my Big Sur Beta 4 stick, installed the latest Mojave updates, used Apple Diagnostics, quick-checked RAM, etc.
I suspected bad RAM or T2 controller because the base system worked but not my much larger installation due to apps and user files. Booting in verbose mode revealed "Type 14=page fault" and later "General Protection Fault" errors, leading to endless "Attempting System Reboot" entries. Reinstalling from scratch and using Migration Assistant, which crashed at the end, resulted in a corrupt users registry, which could not be fixed.
Next, I deleted everything again and reinstalled Mojave from USB stick. Then again used Migration Assistant, but his time deleted all users in the base system which did already exist in my old system. Again, rebooting failed with the same errors.
Lastly and before returning the MM 2020 for repair, I had two options left: 1. check all kext extensions and frameworks in the /Library, and 2. download the latest Big Sur Beta and update the T2 chip to the latest BidgeOS.
I checked all kext files on app relation and installation date, and removed anything not needed specifically or of old date. One removed extension caught my particular attention: trim.kext by Oskar Groth AKA Cindory - installed by the Sensei app, which includes an SSD Trim Enabler.
And... this solved my misery - the clone booted instantly without a hitch! Lesson learned - always clean up the /Libary (the Libary at the top level) before cloning a system disk. "trim.kext" must have been the culprit because it injects code into a system extension at boot time, wasting 3 days of my life. I'm still mystified as to why the same system booting fine with the 2018 MM but crashed the MM 2020, though.
Anyhow, the MM is now running with the latest Mojave macOS 10.14.6 (18G6032) (including Security Update 2020-005 & Supplemental Update) and T2 firmware 18P50402b. Sleep works fine and no crashes so far.