As a result of network interruption during script execution, some of the remote devices never received the ccCopyEntryRowStatus "destroy", so I assume that field remains set to createAnd*. Would there be any danger leaving that "as is", especially considering the next execution will again attempt to set it to createAnd*? On the flip side, what happens if ccCopyEntryRowStatus receives "destroy" when it's not set (or would that be the "notInService(2)" state)?
Yes, you can, and I do in all of my scripts.
No, that won't work. If a row is in a createAndWait state, it must be set to active, not createAndGo.