So, it does sound like "-1" would be the right "Value" for the later MacOS versions with NVMe SSDs that have the "proper" controllers.
No one knows what a proper controller is. It's not specified and SSD vendors can do anything they want, including nothing.
OS Trim is a red herring that you shouldn't bother worrying about unless, like Samsung, you end up stuck waiting for macOS spaceman to run while the drive is worn down pointlessly.
It's likely that WD PC drive Trim simply does nothing and the controller handles wear leveling entirely on its own.
It's a common belief that having the OS issue Trim commands tells the controller something that it couldn't otherwise know: that LBAs are no longer committed to files. But in fact the drive is informed of these details wherever it receives a write, and the drive's LBA to flash translation layer can use the information in place
explicit 'discard' style commands.
Since NVMe the range of "Trim" related commands has been expanded to include other features than wear mgmt, but that's another story. Those features are optiona and beyond the scope of desktop PCs.
It's possible that Apple's Trim implementation adds some value to actual Macs with an OS regimen that's carefully matched to specific Apple SSD capabilities to control SSD wear in a way they can statistically determine fits their product objectives, but Apple storage is a blackbox, so there's no reason for a hackintosh user to expect any value from the feature, and as with Samsung and other drives there are well-known hazards from a mismatch between Apple's OS Trim and 3rd party drives.
