"ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","version":"Kernel 4.19.0-23-amd64"}}}
it is Debian, so not a Mac issue.
I believe you were quick to judge, are looking at the wrong place and thus leading us to the wrong ideas. MongoDB will start serving at that port only when everything is fine, else will shutdown with an error. And, as happens all the time, there can be certain cases that are not anticipated by developers that cause lingering states without a timeout. And I believe this is one of those situations: Your config file is fine so the server passes the initial phases, but gets into a lingering state at storage stage "s":"D4", "c":"STORAGE"
Here, you should now have some new sights. The problem is in the NFS portion of your setup and in one of these sections: nfs driver on this pc (did you changed any related settings?), network itself (any heavy load recently added that slow network?), nfs data host pc (is nfs host healthy?), nfs shared data drive/folder (is data hard drive healthy? data folder?). check all these parts and those I could not think of that are in this pipeline.
PS: as noted above, when you attach/write log files, check for possible sensitive information in them too.