This is important question and worth regularly asking.

Rather than asking about running individual scripts, I suggest stand back and consider an organisation that has workloads on both Linux and Windows. The default might be to use bash on Linux and either batch files or GUI through RDS to manage the Windows machines. Monad started because of the realisation that managing remote servers using a Remote Desktop was insane, and it should be done by scripting. Now if you have a mix of systems it is worth trying to standardise on toolsets. You could put bash or python on Windows, and if you are a Windows user you would think of them as foreign and archaic. Microsoft missed out on the internet, it missed out of mobile phones but it wasn't going to miss out on the cloud. What came as a shock to them, I suggest, is that people preferred to run Linux in Azure rather than windows. So we are back with the scenarios of a mix of platforms. PowerShell is one option to provide a common platform. Regarding legibility of scripts, it is only familiarity with a scripting language that makes it readable. If you have never seen any scripting language then they all look like gobble-de-gook.
PowerShell does two things that Python doesn't do, it lets you easily arrange pipelines. The idea is that you assemble existing scripts and cmdlets and string them together and only code what you need to. In that respect Python is more like an OO language with a library of classes to use. Another thing that PowerShell does it is makes it easy to use existing dotnet modules within a script.
One standout feature of PowerShell is that the pipelines pass objects, not sequences of bytes.

So it is not the answer to everything, but if you work in mixed OS environment it is a decent solution to many problems.

It all depends on exactly how you use PowerShell. As a regular user with no ties to the IT industry, I keep the shell running constantly, it is my primary work application. Since the runtime is always loaded, I don't run into issues with script execution speed.

It is worth noting that I don't use Windows: all my laptops run Arch Linux.

Some people, whether acquaintances or others, might chuckle or make a sarcastic remark, but that usually happens because they don't use PowerShell regularly and fail to appreciate the convenience of both the scripting language itself and the shell.

Of course, I do encounter difficulties from time to time, but nothing stops me from using native utilities as well. Or writing bash/sh scripts to run outside the runtime (in which case they are much faster than their PowerShell counterparts).