And you are simply displaying you do not know the electronics industry at all. All drivers are written for a generic series of devices, any driver not written in this fashion is a waste of developer time and generally quite crappy. (See all those WiFi drivers from 10 years ago.) This is especially the case considering we often modify devices once they're in production, so we need to support several versions with a single driver that supports all. By writing it in a manner that its willing to work with almost anything that fits the specs you save yourself, and above all the user, quite some trouble. And if you have a particularity well working driver it'll be adopted as the de-facto standard. Do you think those Microsoft HID drivers started out in their current shape and form? The nice parts I'm referring to started out as support for Microsoft's own hardware line, they never complained about people using those for a wide variety of reasons. The main reason being that by turning your driver into the standard you gain quite some market leverage, you are the only one capable of signing the new versions of it. So if the functionality needs to be extended you are the only instance capable of doing it while maintaining good support for the older devices.
So no, these drivers aren't specific to a device made by a specific manufacturer. They are specific to a particular hardware-software interface that anybody can freely imitate that infact became the de-facto standard for USB-Serial interfaces. Now if they had stopped at detecting and just saying "sorry, can't work with this" they might have gotten off just fine depending on the jurisdiction, but they went ahead and actively bricked devices. And calling this freeloading is hardly the case, or do we forget that FTDI is "freeloading" on multiple other semi-conductor companies by providing default implementations of their chip-to-chip communication interfaces? If you're going to approach the electronics industry with this mentality you're going to get sued out of existence as a company within years.
This is not an update, this is a very specific modification to damage and disable equipment. There is a very large difference between the two from a legal point of view. So no, they f-ed up and now they have to pay for it.