Not necessarily, it depends on how you configure the your clients and how you configure your service.
If you configure your other devices to use EAP-TLS, then they will only use EAP-TLS and not EAP-MSCHAPv2.
If you want to be really strict though, you could figure out of a way of identifing what OS the device is using (probably through the Endpoints database) and then use a roll mapping and enforcement to block the device if it is not using the EAP method you want.
So for instance, if you have a Windows 10 device and it tries connecting using EAP-MSCHAPv2, then it will be denied. You would then need to identify why the device is using EAP-MSCHAPv2 vs EAP-TLS.
On a side note, the authentication methods defined in the service do not dictate what method your client uses, it only indicates what authenticaiton methods the service will process or handle.