So the thread I had found before was this:
Maybe this would only be relevant in a queue like fashion, where the order does really matter, as when I found this that was a what I was developing at the time.
My worry is that because object will be appended to often and then read at any given time, it may have similiar constraints as a queue. But again, maybe this isn't actually a problem.
My other concern is that if these sub-tasks are rapidly appended to, say in a single for loop, and it's being called from another script on a different thread, how will it handle that. Would I system.tag.writeBlocking on each index of that for loop? Or if I write my changes right at the end of the loop, will another script fail to write to it as its sub-task 'doesn't exist' yet.
These probably only one in a million chance of happening, hence why I'm just seeing what others in a similiar situation do before I start implementing it. TBH, the tag option isn't a bad idea, probably easier to implement in some ways.