No, the guid for the list is used directly by SharePoint to store items in the SQL-tables common to all site collections/sites in a Content database.
If they allowed you to assign that yourselves it would cause problems of people storing information in multiple lists with the same Guid which SharePoint would the read for all of the lists. Which might also allow you to read/write information which you shouldn't have access to.
Even Microsoft got all the checks in place and prevented you from creating new lists with the same guid (also when you moved site collections to new content databases). It would mean that activating your feature in one site collection would disallow it in any other in that database.
So all in all I think it's good you can't control it