Virtual keyboards and "internal" pairing of keyboard with touchpad

[canadaduane]

I'm curious if anyone has insight into how this problem might be alleviated on Linux systems: rvaiya/keyd#353

There are several issues in the above keyd issue related to Linux touchpads:

1. touchpad capabilities across the hardware spectrum can be a bit spotty, so we have a "workaround" in libinput called "Disable-While-Typing".
2. DWT is primarily meant for Laptops that have a touchpad and keyboard (both considered "internal" devices). People experience accidental clicks on touchpads that are configured with "tap to click" (i.e. no mechanical click, just the touch-action/presence of a finger on the touchpad); to "fix" this we disable the internal touchpad while typing, presuming that it is paired with the internal keyboard.
3. We have some software (like keyd above) that creates a virtual keyboard by grabbing the original output, filtering / changing the events, and then acting as the system keyboard.
4. When "replacing" a keyboard with a virtual keyboard, there is no way to signal to libinput that the same DWT for this no-longer-internal keyboard should occur. As a result, keyd's virtual keyboard makes the internal touchpad on a laptop less reliable by causing more accidental clicks with the palm or thumb.
5. The current workaround is to create a "quirks" file describing the virtual keyboard as internal. This is a bit of a lie, and in the above issue, causes other problems.

Is there a better way to "pair" the keyboard and touchpad so that DWT will work, even when a virtual keyboard grabs the original?