For anyone curious, we're using a third party product that uses ISC DHCP under the hood. Any change to a DHCP scope requires a DHCP restart, and we have tens of thousands of scopes as we are a large enterprise grade company. Between broke/fix issues, new branches, and hardware refreshes that require scope changes, we have a lot of changes occurring in our environment. So updating 1800 scopes via the app's CSV bulk import process is tame and fully supported.

Reading between the lines from our vendor support, there are a couple race conditions that can occur when queuing up too many restarts. And as per above, we have a lot of changes going on daily. So after yet another disruptive outage last fall, I wrote a restart daemon that checks if a restart is needed and if so,is a restart in progress. If there is one in progress it skips restarting DHCP, if not then it restarts it. So now we rarely queue up any restarts (a queued up restart occurs when a restart is in progress and someone requests a restart).

Sundialsvc4, good intentions don't guarantee a good answer. Instead of asking for clarifications, you made a lot of incorrect assumptions and ran with them, resulting in an irrelevant post. Hopefully given the above you can see that some curiosity could lead to asking for clarifications, which in turn could lead to a useful response.