Ignore that, typing a new answer...
(edit)
That should be less of a problem then. Is system still writeable? We're going to skip step0, since that's just there to make system writeable and let SuperSU's daemon stay running. If you've rebooted or aren't sure if system is writeable, get a root shell and just type:
Code:
mount -w -o remount /system
Keep the terminal open, and pretend like you just finished step0. Open KingUser, go to settings, and uncheck options then revoke root privs. Ignore SuperSU for now, go back to the terminal, and run step1. If it's mostly successful, open SuperSU and see if it can update now. If it can't, try running step0 one last time, then trying SuperSU. If that still fails, we'll install it manually.
If you're curious about what's going on and why this is a pain for you, it's because KingRoot doesn't like SuperSU and is fighting it. This is why we normally wouldn't install SuperSU until after KingRoot is gone, but it's not the end of the world, just something the script doesn't account for. As long as that root shell is open, you could completely remove SuperSU, KingRoot, and all su binaries and still get root back fairly easily - I goofed when experimenting and did this.