No, don't think so. Also the device-specific code has distinct branches for 16.0, 17.1, and 18.1.
That patch of @tdm is proposed against 18.1. So if it is accepted, it will be only in there.
Currently the driver in 18.1 is still (almost?) the same as in 16.0 and 17.1 so backporting the patch to your local 17.1 tree should be trivial. That may change in the future, as there are several proposals for improving the keyboard driver in 18.1.
I am loosely following that development, but almost certainly will not backport everything to 16.0, as I am in fact quite happy with the current