IIS has db connection pooling built in so I don't see that being an issue. At most you will get the Appeon deployed code using one pool of connections and all the non-Appeon deployed code using another.
If performance of complex SQL is an issue, the logic should be moved into a stored procedure.