Unlike Windows and Linux, Mac OS X binaries can hold code for multiple arch. If a software supports both 32-bit and 64-bit, they simply install a single set of binary files. The OS will decide which binary to load depend on running kernel mode. This actually greatly simplified the deployment.
I have been working on Windows, Linux and Mac. We need different installers for 32-bit and 64-bit for Windows and Linux. But for Mac, we just need one installer.
I don't believe any of that applies for Kernel Extensions.
The relevant (i.e. 32 or 64 bit) extension will be installed when the program/hardware is installed originally.
If the architecture changes, a different kernel extension will be needed.
The other issue is that people might install software/hardware that uses 32-bit extensions (with no 64-bit extension available), then have problems as soon as said theoretical update is installed.