> Ill-formed UTF-16 is replaced with U+FFFD by default, or escaped under {:?}.

Silently corrupting the path seems an odd choice in this day and age, when WTF8 has existed for many years and fixes this round trip bug / security vulnerability

Yes, but WTF-8 is not UTF-8.