However I notice that when you lift the amulet it creates a Amulet.Off before it creates a Amulet.On
This seems to happen when the Amulet has been idle long enough to disconnect, and then when it reconnects it generates the off message. I guess it is something I can (should, will) "fix". It has never been an issue for me because I only use softmute/softunmute. It is a problem for you because you are using a more volatile setup, in which you adjust the volume of your receiver no matter what. Normally, if you execute a SoftUnmute when the SoftMute has not been engaged then nothing will happen.
A fix you could do yourself (until I update the Amulet USB Monitor) would be to keep track of whether or not you have engaged a mute (using a variable and a logic block), and only "unmute" your receiver when necessary.
One thing I notice from your log is that you have the Amulet events assigned to multiple commands that do similar things. You should remove the event from your regular VC listen/standby commands since you have created new commands to handle the events.