To use the example here. What if a plumber is wealthy enough to retire but continues to work because they enjoy it. And what if they then offer a job for free, eg for a community centre or church. Are they then allowed to put an Easter egg in where the pipes explode on Christmas Day?
Comparing adding a fun flag to a system with making a physical bomb is a huge strawman.
The rational behind the exaggeration was to illustrate how even seemingly innocuous software Easter eggs, like an additional flag, have often actually turned out to be security vulnerabilities.
Maybe there is a better way of illustrating that using the plumbing metaphor. Nothing immediately came to my mind but I do apologise if my choice of analogy was more of a distraction than an explanation.
This is a bad example because in what you describe the plumber is making a malicious "easter egg".
In secure software any kind of Easter egg can end up being a vulnerability (and all to often has become one).