I would highly, highly recommend a completely different approach entirely to saving player data, to be honest. This approach of loading user data into a folder as a child of the player will bite you in the future.
You want this functionality:
Player joins → Load data
While playing → Have access, change data, save every so often
Player leaves → Save final data once more
The last thing you want to do during this process is to save data from what’s in the workspace- it’s unnecessary and can become unsafe/convoluted very easily.
To achieve this, you could write your own system for it, but I would highly recommend checking out ProfileStore. It’s used in many, many games such as Grow A Garden & is a very reputable, easy, safe way to save player data. It’s still possible to mess up player data while using, but it saves you the process of writing a complex solution to this.
There’s plenty of tutorials and documentation on using ProfileStore, and using that approach, you wouldn’t be using the structure that’s causing you an issue anymore.