.NET supports proper multithreading (no GIL) and it is also much faster than CPython.
If IronPython gets ported to .NET Core (maybe it already has, I don't know), then you'd get those benefits for free.
I never found platforms like .Net and Java to be low level enough to write systems software, where you'd definitely want multithreading, and not high level enough to be as convenient as Python.
I write in Python and then use PyPy for more CPU intensive services. If I wanted multithreading and instances won't cut it, it would be a pretty hardcore usecase (for a lone wolf like me), I'd most likely also need no GC so I'd reach for something like Rust rather than C#.
I hate to say "no" to learning anything, but to be the devil's advocate this is how I've always seen it.
Having said that, there is probably very little reason unless you're just doing it out of pure interest.