Sounds good to me, I'd been having similar thoughts.  We have some legacy fields that we keep around in json (social media fields that I don't *think* we're collecting any more - need to check community site though.) 

Similarly,  I'd been considering taking it one step further and removing the serialized_object field altogether, adding the relatively few number of additional fields we have to the schema.