Well sorry I should have made my answer more complete.
Changing the UID regularly in and of itself would add an extra layer of security (although “security” in the context of a dumb RFID or NFC chip is all relative). It’s just like passwords really: if you cycle them regularly, they can’t be compromised long term. But it’s not that necessary really.
What the login program brings is decoupling the keyboard input and the chip login itself. That is:
-
You keep your regular login, and you don’t have to use your chip’s UID as a direct password - because quite frankly hex strings are not that easy to remember.
-
You don’t risk autotyping your password in a document, or worse, in a chat window or something if you approach your chip to the reader at the wrong moment
-
You are not at the mercy of the keyboard wedge’s exact output format if you ever change keyboard wedge brand / model and it’s nor programmable
This here post by His Amalness is of interest. Look up the bit that talks about logging in with an ACR122. Assuming you use Windows of course.