Whatever system logic you have on different types, shouldn´t a warning as essential as an uncommanded TR deployment always come on? I would find it rather strange if that annunciation wouldn´t come on until climbing through 1000' ?
It all depends on how a flight deck is designed, based on the interface between flightcrew and flight deck. Alert inhibition is to prevent alerts being presented during flight phases with a high workload (human factors). Only alerts generated in a specific phase will be inhibited, an alert already active prior to entering a next inhibit phase will not be inhibited. For example, if a TR unlock alert would be presented before reaching 80kt, the alert would remain active when accelerating beyond 80kt.
Depending on design, even with certain alerts inhibited at different phases, system design and aircraft behaviour/performance should give clues as to which problem the crew is confronted with. Based on cause, effect and probability of such an event, inhibition is chosen above presentation. These issues are all part of the certification process for a particular design. Once such criteria are established, it all comes down to training for such events.
Green-dot