Thanks for the quick response. I should have followed up last night as I believe I've fixed it, much in the same way you suggested except I didn't have to repackage it. I haven't rolled this out to my prod environment yet so if this is wrong
for some reason please let me know.
All I had to do was deactivate the feature in central admin (I could leave the features a the site collection levels untouched). Make the changes to the customactions.xml file, then reactivate the feature in central admin.
It looks like it's giving me all the results I want. Anything I'm missing here?