I'm sorry if you found my response disjointed or otherwise unhelpful. I was simply trying to provide a possible explanation to the issue that you are having.
To be clear, I can only think of three possible scenarios (in the cloud syncing environment) in which LrC could automatically create VCs:
1. Migrating a Classic catalog to Lightroom in which not all the images in that catalog were previously synced to the cloud, and then after migration sync is re-enabled back in the migrated catalog. That can result in a lot of VCs being created in LrC of all the images that were not previously synced. We can discount that in your situation.
2. Creating a duplicate of an image using one of the Lightroom apps. That would create a full copy in the cloud, but only a VC would be created when that copy syncs to LrC. In that situation, both the original and the VC would show the sync icon in LrC, so again we can discount that.
3. The third situation is a variation on the first one, and is the one I was trying to explain in my previous post. Basically if an image exists in LrC but is not currently synced, adding that image to any of the cloud apps should result in a VC (synced) being created in LrC alongside the original (unsynced). Obviously that's the closest to your situation, but if you are certain that cannot be the case (and if the images in question are new phone captures, then it's difficult to see how that could be the cause), that tends to suggest you are hitting a bug of some description (though not one I've ever come across).
Moving synced images from the download location to a different folder using LrC should not cause this problem. Many users routinely do that without any issue. Similarly moving or copying images between albums in the cloud should not cause this problem.
Unless anyone else has any suggestion as to other possible causes, the only thing which may be worth trying is to reset the LrC preferences file (see
How do I reset Lightroom's Preferences? | The Lightroom Queen), as that can often clear up strange behaviour. But if that doesn't do it, then I'd suggest filing a bug report to Adobe using the link at the top of the page.