CRCs and custom tables

Would it make any sense to use CRCs for storing data in custom tables without actually saving a resource in site_content table?
Idea is:
Create custom table, Create CRC, override create processor for resource to only save in custom table - nothing saved in resources table at all.

I am considering this because it would enable input through Resource panel and TVs (with all the benefits of validation and such) and eliminate all the drawbacks. Basically, this way what should be one record in table would be one record in table.

I am not sure that it is good way to go so I would like to hear your thoughts (or facts;))
Thanks