Yes and yes, Tim. All businesses change from state A to state B by way of a transition that weighs the downside risk against the upside gains. Your dimmer analogy is right on.
The stress these days on the development supply side is the loss of market supply at scale for on-premise. To parallel the electricity analogy, the cost of backup generators today is way more expensive than if everyone had a generator for primary power. The same holds true for the physical on-premise IT parts.
Developers have to follow the dimmer and move their finely tuned code base from state A to state B just as carefully (change, retune, change, retune, change, retune,...).
I would run ProcMon to see why there is such delay after connecting the device. In ProcMon you can look at the Duration column to see what takes so long.
Thanks MagicAndre1981, Gov, and Larry. I watched the events in ProcMon and narrowed down the time frames. It appears that the networking stack to the device takes 3 to 7 seconds (varies with each device connect) to become usable. I setup a CMD window with "ping 169.254.2.1 -t" and could see where the device was unreachable (disconnected) then general failure (device was just connected) then ping results (device networking established) then after 3 or 4 successful pings the device's networking was generally available to other applications.