Much of this is most likely due to the use of the drivers' CUPS plug-ins to achieve both User Interface (like the Finishing, Quality, and Special Features options for the Canon USA driver, and the common Fiery interface for the imagePASS driver) and operational functions. Many of these plug-ins attempt to establish a connection with the printer on the other end because, tradtionally, a MacOS client has only ever attached to a device (I know, I know...we don't, but in environments that don't have print management software, it's all direct to printer). In fact, on the imagePASS installer I downloaded, if you don't choose the "just install driver" option, only allows you to specify a Fiery-backend destination; you can't just set it up to any old IP address or host name. Rude!
At any rate, a dismal part of all of this is that the communication bit has to time out on the MacOS system before you can move to the next thing. And if the communication isn't successful, sometimes complete functions are made unavailable in the Print dialog box. Yet even more dismal, sometimes a single CUPS plug-in does more than one thing, so simply removing it from the PPD as a necessary resource causes failure.
I know that there are some issues using the "Generic PPD" (notably, no color choice, and a limited paper selection), but on the MacOS, given the proclivity of the manufacturers to wrap so much outside the PPD for MacOS drivers, it may be the only stable option available.