Moving Site Collections to a different managed path

We are looking at the need to rename some site collections and move them to a different managed path. 

We are renaming the site collections to remove spaces and reduce the character count.  We are moving them to a different managed path to use utilize the wildcard managed path as opposed to the explicit managed path.

I have a few questions I need help with.

1. Is there a recommendation for the number of sites listed under on wildcard managed path? We know the suggestion, if not limit, for explicit managed paths i2 less than 20. Does that hold true for site collections under a wildcard managed path?
2. Is the limit of wildcard managed paths also less than 20?
3. When moving a site collection to a new managed path and then subsequently moving the sites beneath that site collection, will the URL for the sub-sites automatically absorb the new managed path or will they need to manually changed?\
   • Example: We rename a site collection from Enterprise Communities to EntCom and change the managed path fromhttp://this.that.yes/Enterprise%20Communities to http://this.that.yes/EXEC/EntCom. Will the sub-sites adopt the new http://this.that.yes/EXEC/EntCom wildcard managed path automatically when they are moved?

As alway, thank you in advance and any assistance is greatly appreciated.

Doug