You're building complexity where there is none. Once again, the only reason you have an ODBC connection is for connecting to a data source that is not Access. For example, I go through an ODBC connection at work to connect to a DB2 database. This doesn't make it faster -- it just makes it possible.
Think of it this way. I want data from a DB2 database. I am using Access, which is not compatible with DB2. The ODBC Driver is the translator between the two. Therefore, from Access I send a query. The ODBC Driver takes that query and translates it into something DB2 can understand. DB2 does its thing and is ready to send the results back to Access. DB2 sends its results to the ODBC Driver, which translates it into something Access understands. And all is good with the world.
Without the ODBC Driver as a "middleman", you can't connect to other data sources that Access doesn't inherently understand. That's all it is. There are SQL Server Drivers, FoxPro Drivers, DBASE Driver, etc. All of them do roughly the same thing for their associated data sources. Unless you're using something that Access doesn't inherently understand, there's no need for an ODBC Driver or any other "middleman" as it were.