Exactly.
No need. This one has already been fixed, just not released.
That’s what it does. But that means the documentation which comes before it ends up belonging to unparsed garbage instead of belonging to the symbol found by the scan. The code that fishes for the stray documentation has already been improved somewhat since the release, but dissecting garbage interference is clumsy and unpredictable. It does not cause outright failure, so you can just put up with missing documentation comments for now if that is what you would rather do.
You are correct that they are not the same, and also correct in your understanding of each. I mentioned it as a viable workaround in your specific case because ABI resilience is irrelevant to your package. Your package does not vend any dynamic library; its product will always be statically linked. Such use was one of the major driving forces behind SE‐0193 in the first place.