Devil's advocate: If you're using PowerShell on Linux you probably mean to remain compatible with a Windows workflow. PS uses other unix aliases such as ls and cat. But these all have different semantics than their namesakes. So if PS on Linux deferred to the native tools it would break compatibility with PS on Windows where those tools aren't typically available. If PS wants to remain true to its own goal of being a unified toolchain for cross-platform development, it should stick to its own implementations even if it perturbs some people who are primarily *nix developers. Because developers not working with Windows are not the primary audience of PS.
Consider that PS also aliases DOS commands such as DIR but is not compatible with the COMMAND.COM commands.
Consider that PS also aliases DOS commands such as DIR but is not compatible with the COMMAND.COM commands.