Hi,
In general I concur - and they kind of automated the original installation with the OneInstaller, but this currently only covers a somewhat restricted installation layout.
The engine has a multitude of possible setups (e.g. various ways it can be distrubuted across one or many servers) and also a load of
cruft legacy components, with .ini files that are not entirely easy to parse and have their syntax vary with engine versions. I figure it would be no easy task to automate this retroactively without creating something that occasionally blows up.
For this and related reasons at least parts of the community also advocate for doing manual updates instead of ZDU updates, at least for larger updates. It's a good while ago but we had issues with ZDU (the details of which are documented somewhere in the forums, if it matters), leading us to only do manual updates for the time being. We manage to do minor updates (12.x to 12.y and such) with two hours of scheduled downtime and usually in about an hour of wall time, but your mileage may vary with your particular setup.
Best,
Carsten