I prob went too far with the example, but my point is that we should use the manufacturer's procedures and not make them up ourselves. Altitude is not the only thing we need to think of before doing anything that might upset the applecart. By writing and briefing "Nothing until 400 feet" primes the non-thinking pilot (more and more of those all the time) to react to the altimeter. Losing the airplane at 400 feet or at 1500 feet in a big airplane will have the same result. Boeing says "when safely under conrol" and that is all that is necessary.
And for the 400/800 feet boyos, what do you do if an engine goes into reverse on lift off, or two engine out of 4/3 fail at the same time? You will never even get to 400 feet if you don't do something straight away.
I fly with too many FOs (who will be captains soon) who cannot think or prioritise. They are the products of the "rules and numbers" managers and have never learned. But they know the rules, and with AIMS and such, fly in fear of being caught breaking a rule, no matter how minor or stupid. I have them overbanking and descending through the altitude and not even noticing because they must get the seat belt sign or landing light switch on, since that is the "procedure".
Personally I would probably wait until 1000 feet or so before shutting down an engine for a fire warning. I object to requiring an altitude for the action, since that is not a correct nor sensible way to decide.
I have said it before and I say it again: You cannot legislate safety.