Yes, you'll have to drop the RunAsync (missed that switch in your line of code).
But why are you using the RunAsync here, does the actual cloning from a template take that long ?
Remember the customisation will only start when the VM is powered on.
You can of course also monitor the Task that was returned when you launched New-VM with the RunAsync switch.
You can do this with the Wait-Task cmdlet, or you can check the State of the Task
See Re: Script to wait for Clone Task to complete