The fact that the hard-link exists doesn't guarantee that the two stores aren't out of sync, it is just an indicator.
It looks to me like all the drivers in the remote desktop client package are corrupt. That may also extend to the remote desktop service package, because they are both installed at the same time by a single KB (KB2592687). That is the "RDP8" (remote desktop 8) package. If my guess is correct, then you will need to delete the entries for all of these drivers:
bth.inf
tsgenericusbdriver.inf
tsusbhubfilter.inf
termkbd.inf
termmou.inf
There is a 2nd issue at work here though. The RDP8 package you have hasn't actually been superseded. Instead, a package that it depends on has, and when the package that it depends on is scheduled to uninstall that makes RDP8 also eligible to be uninstalled. This package is known as the "DTLS" package (KB2574819). Most likely you have the v1.007 version of the DTLS package, which has a bug in its packaging that allows it to be superseded and removed, while RDP8 still needs it. To fix that you can install the v2.000 version of the DTLS package from here: http://support.microsoft.com/kb/2574819/en-us
My recommendation is to go through with the cleanup, delete the registry entries for the above inf files, and allow the uninstall to complete. After that, I'd suggest you run the system update readiness tool (checksur.exe) to see if there are any other corruptions that need to be repaired. Then download DTLS v2 and install it, and re-install the RDP8 package. (available here: http://support.microsoft.com/kb/2592687/en-us)
If all goes well, that should eliminate the known corruption issues.