The first dongle I ran into was in about 91. I called the company that produced it when the company that produced some high end printers software could not tell me why there were problems with the software and I thought the dongle was at the root of the problems. The company repeated to me that the dongle could not cause any problems and that the code was completely secure. A few weeks later, I sent them the source of the dongles code and a cracked version of the software that ran without problems OR the dongle.
Cubase is repored by Steinburg to be completely hackproof because it uses the Ilock dongle. Steinburg asserts that Cubase has never been cracked. In this case the Ilock is used in place of authentication. I can send anyone a copy of Cubase that is cracked. Most of the people I know that use Cubase, purchase the program and the Ilock and then use the cracked version because the cracked version does not intorduce the problems that the dongled version does. The only difference is that only the dongle is cracked and removed from the software.
Waves uses the Ilock in the same fashion as Cubase above. The same story applies.
As to reducing or eliminating a department, it does not because now you have to increase your tech support department to handle the flood of calls when your dongle screws up someones machine. Or to put it another way, you decrease the team handling authentication, but have to increase the support department. This is a zero sum gain.
Dongles are far from secure and they just increase complexity.