The referenced article is from 2023, so maybe the argument is obsolete…
Anyway, I agree with you that just because the error message is UTF-8 related does not mean that it is a character code issue.
I hope it’s a problem that can be avoided by modifying the options or code without changing the dataset.
It could even be some kind of bug that has never been fixed because it can only be avoided by changing the dataset.