Does SP 2016 on-premises still require PowerShell script to be run prior to async SC creation?

VesaJuvonen, I did confirm that this is still the case on-premises in SharePoint 2016.  However, in following the instructions in the blog, I ran the PowerShell script as directed, but still receive the following error:

{"Cannot find stub for type with id \"{268004ae-ef6b-4e9b-8425-127220d84719}\". The specified server may not support APIs used in this operation."}

This error appears http://sharepoint.stackexchange.com/questions/105122/sharepoint-2013-high-trust-app-site-collection-provisioning before running the PowerShell script; that is to say, the assembly is still not being loaded.  

I tried updating the script to use version 16.0.5806.1205 of the Microsoft.Online.SharePoint.Client.Tenant.dll assembly (this is now the version included with the PowerShell for SharePoint Online package), but to no avail.  I also double-checked that the site collection is in fact set as a TenantAdministration site.

Any pointers?  I'm concerned that I am missing a prerequisite somewhere.  Could this same error also be thrown if the client context is not properly created?