HWIDChanger is a Windows tool, and macOS works differently enough that it is worth explaining where things stand.
How macOS handles device identity
Instead of a Windows-style HWID, a Mac has its own Hardware UUID, alongside the Apple ID and — on modern machines — keys held in a secure enclave. Mac software that uses licensing still reads familiar things too: the MAC address, disk and CPU information.
What can be changed on a Mac
On older Intel Macs the Hardware UUID could be altered through low-level settings. On Macs with a T2 chip or Apple Silicon (M1 and later) that route is closed — the UUID lives in a secure enclave and is not modifiable. What remains practical on a modern Mac is changing the MAC address, changing the hostname and clearing licensing caches — enough for basic scenarios.
Windows on a Mac
If you run Windows on a Mac — through Boot Camp or a virtual machine — HWIDChanger works normally inside that Windows environment. It changes the Windows-side identifiers; it does not and cannot touch the macOS layer.
The honest summary
Apple's locked-down design means a Windows-style HWID change largely does not apply to a native macOS install on modern hardware. That is a deliberate Apple decision, not a gap a tool can close.