Comment # 18 on bug 990356 from Neil Brown

Once you get nfs-client 1.3.4 installed, those changes should stay.
The delays caused by rpcbind not running should be in the next kernel update,
though I don't know how the timetable for that works.

rpc.statd:
            Starting NFS status monitor for NFSv2/3 locking...

will always be started by default, but it will fail if rpcbind isn't running. 
A failure of rpc.statd won't cause nfsdv4 to fail.

You probably have rpcbind.service still enabled.  I'm not sure if you did that
or some system thing did.  Anyway, if you
  systemctl disasble rpcbind.server
and keep rpcbind.socket masked, it should start at all.  Then "NFS status
monitor" won't successfully start either, but nfsd will.