Nope. Not yet anyway. That's really something DNSCrypt in it's present form lacks. DNS is so fundemental, that there needs to be a failover.
I'm thinking about doing something that checks the server status and reconfigures dnscrypt to another service if it can't reach the currently configured...
Now with more automation - I've made a script to handle the installation and configuration on debian like OS's, have a look here: http://simonclausen.dk/2013/09/dnscrypt-autoinstaller/
The same way you rebuild trust in any other relation - don't keep secrets, be consistent, show improvement, etc, etc.
But I have to say that you've done a good job of making it harder for yourself by posting this.