> The wide APIs accept and/or produce invalid UTF-16 in some places (like filesystems). There's no corresponding UTF-8 for invalid UTF-16. Meaning there are cases that lead to loss of information and that you simply cannot handle.

There's WTF-8 - too bad that's not what Microsoft chose to use for their universal 8-bit codepage.