EAP-TEAP

 

At least with Windows 10 build 2004 and ISE 2.7 Patch 2.

Using TEAP for EAP Chaining

https://www.ise-support.com/2020/05/29/using-teap-for-eap-chaining/

Unfortunately there is no native support for EAP-TEAP in Group Policy Objects for Windows Server 2019 and below. There is a workaround however to use TEAP anyway. In short, we will configure TEAP on a Windows 10 Client and export the settings. This file can then be used to import the settings into a GPO. Even if they are not available for selection in the GUI.

Create TEAP GPO using Windows Server 2019 and Below

https://niksec.com/create-teap-gpo-using-windows-server-2019-and-below/

TEAP for Windows 10 using Group Policy and ISE TEAP Configuration

https://community.cisco.com/t5/security-knowledge-base/teap-for-windows-10-using-group-policy-and-ise-teap/ta-p/4134289

Certificate-based EAP methods like EAP-TLS are generally considered more secure than password-based methods like PEAP-MSCHAPv2. See this blog for details on two.
Machine auth using EAP-TLS is common, but lots of organisations find user certificate-based user auth too difficult to manage due to certificate enrollment, expiry, etc. TEAP supports using EAP-TLS for machine auth and PEAP-MSCHAPv2, so it's a viable option to mitigate user certificate concerns. It also provides the added benefit of EAP Chaining. I would suggest reviewing the Using TEAP for EAP Chaining document and comparing it to your setup.
It's not very clear in the UI but, in the Client Authentication section of the supplicant the 'Primary EAP method' refers to the User auth state, and the 'Secondary EAP method' refers to the computer auth state.