One status table for all models?
I would think so. Especially if you don't want the status published on users.. If you want to add a status to one, you're going to special case code for one of the consumers to exclude?

I would keep it simple -- two separate tables. Or if they're immutable (you won't be deleting and updating) status's and you're only using them on the one table, you can use an ENUM macro/check constraint.