I have found a work around...may be a waste of time if seeding is going to be included in a future versions. I am not going to provide step-by-step details, but the general idea was that I setup a "portable seed cloud connect server". This server can be taken to a client site to get an initial seed. The "seed server" is running Veeam Cloud Connect and has identical settings (think repository, tenant name/pw, certificate, etc) as the production Cloud Connect server. Configure VWA to backup to cloud connect using the host name of your production cloud connect server but make sure that you edit DNS for client site so that the host name resolves locally to your "seed server". Once the initial backup has completed, take the seed data to the production cloud connect server and upload to repository making sure to put all of the data including job folder into a tenant folder of same name on production CC machine. Make sure to rescan repository and make sure that you have setup a tenant with identical name, quota, concurrent tasks, password, etc (may not matter but just to be safe). TIP: make sure that the repository you are using is set to automatically import backup jobs so that a rescan will see the newly copied data.
On the VWA side, after you have adjusted DNS back to resolving production CC to the actual production server, if you go ahead and run the backup job, it will most likely fail due to a repository ID mismatch. This is ok. What you need to do is simply open VWA control panel, choose configure job and just step through each step without changing any settings. all the settings should be identical including the certificate if you followed my advice above. Once you have stepped through all of the settings, VWA should reach out to the CC server and establish the connection. Now you should be able to run the VWA job, it will see the initial full job on the CC production server and run an incremental.
it would be a good idea to do this on a fresh VWA install or at least reset the VWA database if you want to try it out. Also, I tried to do the same thing with the free Endpoint but it did not behave in the same way...I tried to do Endpoint ---> Veeam local repo. Then Veeam local repo --->seed CC backup copy. Copy data from seed CC to production CC but it would run a full backup copy job each time. Oh well.