Is it possible to map BYOC trunk failover latency to WFM schedule adherence?

Is it possible to correlate SIP 408 Request Timeout events during BYOC failover with agent schedule adherence metrics? We manage 15 trunks in APAC. When primary registration drops, the ~300ms switch to secondary causes brief dead air. Current WFM reports flag this as idle time, skewing adherence scores. Does the Genesys Cloud API expose a specific event code for carrier switchover latency to exclude from adherence calculations?