Hi Julio,
The steps you mentioned are correct.
Once you assign the services to the new certificate, it will automatically overwrite the old certificate services, hence you don't have to worry about it. Normally we would keep the certificate there itself for sometime and Delete it from EAC later.
[You can't
remove the certificate that's being used. If you want to replace the default certificate for the server with another certificate that has the same fully qualified domain name (FQDN), you must create the new certificate first, and then remove the old certificate.]
Just to confirm, you have requested the new wildcard certificate from the EAC and import steps are also from EAC only right.
Nice guide for "SSL Certificate Installation for Exchange 2013"
https://www.digicert.com/ssl-certificate-installation-microsoft-exchange-2013.htm
Also the service disruption will be very short(Assignment step). But if you have the namespace loadbalanced with 2 servers, you can do this one by one. Without users noticing the c