In a couple years you won't have to bother with that. The device will connect to the ID chip embedded in your body when you're born. And this will be a one-time hard-wired coupling for that device when it is first turned on.
A bit of a tangent, but your worst case answer here is the culmination of all the secure boot and remote attestation concepts.
What would stop it is a combination of not being able to buy new hardware that will even boot the modified kernel, and not being able to get vintage hardware to connect to any public ISP etc. due to being unable to attest its validated boot chain information, signed by a required modern hardware OEM key.
So you would be stuck in some kind of underworld of vintage folks attempting mesh networking between themselves. Then, because of basic market forces/economics, there will be a dwindling amount of software that is able to run in such environments. It will become the esoteric realm of old-school hobbyists who don't need to run any commercial apps which require ABI/API features of the modern commercial OSs which require this boot chain of the modern commercial hardware, etc.
What they're trying to do is force web sites to require this "service". So if you're running Linux stripped of those packages, your browser will effectively be nerfed -- content hosted by companies doing business Europe or the Anglosphere would be unavailable or "kid safed".
Most people will eventually just give in when that happens.
They might force the Linux kernel to add a value 'age' to the couple username/password. Although in Europe OSS is exempt from age verification obligation.