Note that my rig is running with HPET DISABLED via ACPI patch (HPET._STA=0 just like a real MacMini8,1). See my reasoning here. I'm not sure if this HPET setting affects these results. I also use RtcMemoryFixup.kext with custom rtcfx_exclude range (with CLOVER, I did not use "Fix RTC"). I also have both DDR4 memory banks populated (I have found that single-bank performance is less).
I have found on my MacBook Pro 2020 that HPET is still in use by macOS in my System DSDT by just opening MaciASL and search for HPET.
See this:
Device (HPET)
{
Name (_HID, EisaId ("PNP0103") /* HPET System Timer */) // _HID: Hardware ID
Name (_CID, EisaId ("PNP0C01") /* System Board */) // _CID: Compatible ID
Name (BUF0, ResourceTemplate ()
{
IRQNoFlags ()
{0}
IRQNoFlags ()
{8}
Memory32Fixed (ReadWrite,
0xFED00000, // Address Base
0x00004000, // Address Length
)
})
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (OSDW ())
{
Return (Zero)
}
If ((OSYS >= 0x07D1))
{
Return (0x0F)
}
Else
{
Return (0x0B)
}
Return (Zero)
}
Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings
{
Return (BUF0) /* \_SB_.PCI0.LPCB.HPET.BUF0 */
}
}
It looks almost like the SST-HPET.aml generated by SSDTime. I have had no issues with using AWACS-HPET but I have reverted to use SSDT-HPET with the patches on my build again.
Have fun with your new Desktop b.t.w.