History says it wouldn’t be that important. Google found two forum uses suggested – none done. Issues got one use in 2014 for kenkendk that was seemingly useful. I see option left in PR 5540.
In my view, there’s a general lack of protocol troubleshooting tools, and I don’t think .NET has a Network Tracing in the .NET Framework replacement (last I looked). That was sometimes good, although far from ideal, even ignoring the difficulty of trying protocol-level interoperability debug.
There might be some ways to get ETW to help, but I haven’t dug into that much. Packet tracing typically can’t help much because the connection is encrypted, but internal views can avoid that.
In this specific topic, I lost interest in protocol troubleshooting when destination was seen empty.