Sorry to hear you're running into issues - I have to admit that I never use NFS, so my experience is rather limited.

What info did you enter for the share?
(obscurify a few details if need be)

@hans Same info as on the command line, except that I broke it up into the server portion (newtokyo2.cfa.harvard.edu) and the path (/vol/vol3/ssxghome).

Did you enter "newtokyo2.cfa.harvard.edu" or "nfs://newtokyo2.cfa.harvard.edu" ? (the latter won't work)

I entered the first one.  I've never seen that second notation, and after selecting "nfs" in the drop down, I was assuming that the program would know how to format the call/command.

Also, just FYI, this mac has the Apple M2 ultra CPU, not intel.

Oh good! Just making sure 😊 
I'm running it on Apple Silicon as well.

Could you check and see wha the settings for this share are under Advanced Options?
One can mount with a system API or a commandline mount.

For example, I used these settings way back when I implemented the NFS support.
As mentioned: I do not use NFS at all, so I'm relying on limited testing and user feedback (again: apologies for the inconvenience).

See if these settings help your situation as well.

So, I tried switching from "system call" to "command line" and tried the options "nfs" and "-o nfs" and none of that worked, BUT

When I tried switching from custom path (/home) to Default (/Volumes), it immediately mounted the share.  
I would have greatly preferred to have it mounted on /home, but I think I can live with this. 
I have another question, but I will start a new thread for it.  

Oh that's good news! Well, for now anyway.

As for mounting on /home; 
Does that even work when manually mounting?
When I look at /home, I see this:

lrwxr-xr-x    1 root  wheel    25 Sep  1 18:55 home -> /System/Volumes/Data/home

Basically telling me to probably not use it to mount a share in as it is used by the system (Apple having all kinds of things locked down maybe)?

What I usually do, not required of course:
- have system calls mount in their default path (/Volumes/), which is for the majority of mounts
- have command line mount mount in ~/MountPoints/, for oddball mounts that require command line mounts for them to work

Did you try System Call mount, with or without custom path? Just being curious if the API call handles it properly. I do recall for NFS needing to use the command line approach, but it has been a while that I tinkered with that.

p.s. if you're OK with it the solution, then please let me know, or click the "Solved" button on top of this thread. 😊 

Yes, when I manually mount it, it mounts the nfs shared home directory (ssxghome) over the link. 

The problem is that manual mounts don't survive a reboot (thus my OTHER topic that I started). 

For your second question, I was trying system call mounts at first with custom path, causing the initial mis-behavior,

After you suggested I look in advanced options, I tried the command line mount (no go), then went back to system call but with the Default (/Volumes) option, and that's what finally worked. 

Apologies for being confused.
You're saying you can manually mount against "/home" or are we not talking about the same "home" 😉 
What does the output of "mount" (in Terminal) look like after you did a manual mount (your way, before you used ConnectMeNow) and when using ConnectMeNow (command line option)?

Yes, when logged in as the privileged user (root), I can run the command line just like I showed at the top of this thread, and it will mount the home directories to /home.  In typical UNIX/linux fashion, there is no output for success. The terminal simply returns the command prompt. 

Interesting - I'd think that would (on my machine anyway) potentially cause problems anyway. But you having done this may indicate that I'm wrong about that.
I thought it more common under Linux to make mount points in "/mnt"?
I suppose I never really did dig in too much, and assumed "~" was home 😊 

Learn something new every day I suppose.

it is. Linux likes to put misc mounts under /mnt, and ~ DOES represent a users home directory (as defined in the /etc/passwd file, which macOS appears not to use), but when user home directories are stored on the network, they are usually (nfs) mounted to /home.