Nick's code is already wrapped in exception handling, so I doubt it would ever make the designer unusable if something failed, but even so, I'd recommend modifying the client tag that applies this to include some sort of way out just in case somebody expands this later and accidentally introduces a breaking change. I could imagine scenarios where faulty initial change scripts of this nature could brick the designer.
On the client tag, it could be as simple as:
# Exclude at least one admin account
# ...so it can access an unmodified version of the designer if need be.
if username not in ["recoveryAdmin", ...]:
# Apply patches
...and hopefully the management team that is pushing for these kinds of metrics doesn't end up using them to lay off those who understand how this client tag patch is applied.