I think this issue is caused by --daemon not passing the credentials to unlock your rclone.conf properly.
Suprisingly --daemon is a really complicated feature - Go absolutely hates forking so there are a lot of workarounds here.
I think this used to work properly. At least it is working well enough to unlock the config once - why not again?
Not using --daemon would be a useful test.
You could use screen or tmux to start rclone and leave it running. I often do this
screen -dmS rclone rclone mount ...