Unless any setup should be different from v1.2.2 (of which I have seen no documentation) - no, nothing has been changed on my side.
During the recent update, I watched it 'closing down statd', 'enabling stat' and then 'starting statd' - which then gave an error.
It has worked perfectly for me from the very first lmde and up to this last update (and some other distros as well).
And fyi - 'bleeding edge' archlinux still uses v1.2.2
As to the actual arguments passed to rpc.statd, I have no idea as it is started well beyond my control - its started as part of the boot-process because the nfs-mount has been activated.
As I said - I was _watching_ the sucker being updated and returning an error upon restart.