It’s just different. And pointing out there is a long list of “missing commands” with slow progress from 2018: http://forum.mikrotik.com/t/built-in-function-library/117288/1
Now if your trying to scan other hosts, you can use a container on ARM-based Mikrotik with “nmap”, “nc” or whatever, that might help some here.
“netstat” is tricker… Certainly no “netstat -l” – since you’re right someone does have to connect to see if it’s open connection… Now I guess “nmap” from a container could find all the open ports on the Mikrotik 
.