encoding subtly different between 2019R1.1 and 2019R3

Yes. Although the root of the problem seems to be Unicode allowing both decomposed and precomposed characters in the first place. But given that situation, treatment should be transparent.

Just out of curiosity, does FolderItem.PathTypeURL give both precomposed and decomposed characters, or does it convert them to a single type?