Feature Request: Custom Object views

I have a custom object that is a many to many table. We have customers that have multiple accounts, and inversely accounts with multiple customer. At present, we handle updating the data as a joined SQL export then import via API to the custom object end point.

For managing a custom object, we'd like our agents to be able to search either account name/number or customer name/email. This is possible with the custom object UI since the view indexes those details.

However, to simplify other backend uses of this data, it becomes incredibly inefficient to develop methods that rely solely on one to many indices. It seems like the only solution is to have three separate custom objects: many:many customers/accounts, one:many customer:accounts, and one:many account:customers.

To create the three separate objects (that would all have the same data), we need to run the import job three times tweaking the data each time. It would improve manual effort, data integrity and API usage efficiency if custom objects (which I think are all basically flat, tabular) could also have custom views associated with those objects. 

("views" as in database, not "Views" as in agent workspace)