My understanding behind these two considerations are as follows:
The unique names is to avoid any events that add instances of anything to find two matching results, hence acting out the result (addInstance) on both. If there's more to it, please let me know.
In that case, no, all fields have unique names. Across the entire form. Even outside tiers of hierarchy.
Pathing specifically to the form would make sense also if I went to pass a script on an event that found multiple results of "xspread". Still, xspread is one isolated subform, nothing else shares that name.
Further, the problem is at the document initializing stage. Basically, the first instance of xspread doubles itself every time. So even if I start off the form with 0 instances of xspread, only to be added, it will during the filling out of the form. But after saving and sending, the opening of it initializes the first instance of it and doubles it. There is no other condition that forces xspread to double itself again.
If I add a new empsheet, the first xspread works correctly through and through. It's the empsheet[0].xspread[0] that causes this problem, every time.
I'm going to try running a document initialize event that checks the count of form1.p1.empwrap.empsheet[0].spread.xspread[0], and if there's more than one, set it to 1. But it still makes no sense why this is happening.