Yes, a .NET Thread maps to a native operating system thread on all current CLR hosts.
There's an option to map it to something else in the hosting api through the ICLRTaskManager interface, like a fiber, but that is not actually implemented in any of the main-stream hosts. The SQL Server team at the .NET 2.0 time frame attempted this but the project was abandoned when they could not make it reliable enough. This was not tried again. Technically you could run into a custom hosted CLR, started by an unmanaged program, that implemented this mapping but the odds are rather low.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…