This may be because of how the kingdom was destroyed? There were no sieges deployed at the time of destruction. It was burned rather than sieged to death. Devs should look into this, and whizzle you should put in a ticket with tech support, and if you already have please specify that there were no sieges deployed when the castle was destroyed. I'm pretty certain that may have something to do with it, and if the devs are able to replicate the glitch they might have a better chance at fixing it.