After rolling back in my local development environment again and rethinking, now I strongly think the problem lied in WordPress itself. Because the day I found the problem I updated the WordPress 6.0.0 in my local development to 6.0.1, and then the problem showed. Now I cannot repeat it and I guess it is due to the translation files have been updated in the WordPress ZH_CN 6.0.1 package.