Hi Toothpicker!
Did you ever find a solution for this particular issue? I am in the exact same boat at a new company. There is a corrupt page in a seed db that DBCC CHECKDB didn't recognize and this has been used to create a gazillion other databases which are all unable to be encrypted.
Thanks,
JB