The OA3xOriginalProductKey method returns the Windows OEM license key stored in the BIOS for pre-installed machines where they used that method to store it - most OEMs do this because this is the only way where they DON'T need to physically affix a sticker with the key on the machine which saves them time.
If there's no Windows OEM key in the BIOS it will be empty and if you've reinstalled using a different key it will give you the wrong key! It is useful as a way to access the key that comes with the hardware on most newer OEM machines but is no substitute for actually checking what license key Windows actually use.
And the third method usually? sometimes? returns a "digital key" that's only valid for the specific install - there's no real use for this since it can't be used even on the same hardware after a reinstall!
So really, only the first method should ever be used, there are other programs and tools that will work but there's no reliable methods that doesn't use tools!
So you might as well use the most well-known one, Magical Jelly Bean KeyFinder.
And in my experience Microsoft will 99 times out of 100 automatically detect and apply the correct key (as long as you select the right Windows Edition) even when doing clean installs on existing hardware even if you don't use a MS account for login and it doesn't have a BIOS stored license key. If it does have the stored key it goes up to 100%.
OTOH this stored BIOS license key can be a problem if you're trying to do a clean install of a DIFFERENT edition of Windows (like Pro while the machine came with Home). Windows install bypass the Edition selection when it finds that key in BIOS storage, the workaround for this is to edit one of the file on the install media which forces it to always ask.
Note that it does this (install "wrong" edition) even if it later in the process shows that Microsoft will find and use the license for the other edition without logging in on an MS account, it does it by looking up various hardware serial numbers but this happens much later in the install process and only works if you've forced it to the right edition.