Sorry, I didn't get notifications about your questions and only saw them today.
1) Yes, in the final version this attribute is called "alias".
2) You need to make the management ceriticate available to the role hosting Wasabi. This means deploying it through the Windows Azure portal and adding it to the list of certificates for the role. Then you also have to specify that certificate's thumbprint for the subscription element in the services store.
3) You can have Wasabi autoscale itself (the block is prepared to deal with multiple instances of the autoscaler - we are using an execution lease), but that's not necessarily something that you would probably want to do. The technical reason is that it's better for an autoscaler to be running continuously in an instance. If you modify your app and decide to redeploy, the autoscaler will need to be interrupted and redeployed as well. Thus, it's better to run in its own role - an extra small worker or web role would do.