New state for when host is collecting debug data?

On POWER based servers we have instances where the host, or the hypervisor running under the host, collects debug data for some sort of critical failure. This is very similar to the situation where a "Nmi" "ResetType" is used against v1/Systems/system/Actions/ComputerSystem.Reset.

In our case, this debug collection can take 10's of minutes. The debug collection can occur with or without user interactions. If a critical fail is detected then the system will automatically begin collecting the data. A user can also request the data be collected. We'd like a way to communicate this is occurring to the user because the host will no longer respond to commands once it begins collecting this data.

The current States are the following:

"Absent": "This function or Resource is either not present or detected.",
"Deferring": "The element does not process any commands but queues new requests.",
"Disabled": "This function or Resource is disabled.",
"Enabled": "This function or Resource is enabled.",
"InTest": "This function or Resource is undergoing testing.",
"Quiesced": "The element is enabled but only processes a restricted set of commands.",
"StandbyOffline": "This function or Resource is enabled but awaits an external action to activate it.",
"StandbySpare": "This function or Resource is part of a redundancy set and awaits a failover or other external action to activate it.",
"Starting": "This function or Resource is starting.",
"UnavailableOffline": "This function or Resource is present but cannot be used.",
"Updating": "The element is updating and may be unavailable or degraded."

"UnavailableOffline" seems like the best option at this point but it's not as crisp as we'd prefer. I'm wondering if the DMTF would be open to a new State for this, something like "CapturingDebug"? I know the BMC would also have a similar scenario so this new state could be applicable there as well.