Apologies for the delay in responding - We checked this internally and got the below response.
The problem with using the msteams: protocol directly is that if the user doesn't have Teams installed, the protocol launch would most likely fail (at least it would on Windows/Mac). The launcher provides a way for the customer to acquire the Teams Client if they don't have it installed:
Hence, it's not recommended to use the msteams: protocol directly unless the launch source has some way to ensure that the Teams Client is installed before executing the deep link.