This is not supported at the moment. In general LLBLGen's queries are pretty efficient and we have very few problems with query execution speed, as long as developers use the normal, sensible principles that you would when querying any database - ensuring indexes are in place, filtering queries to only request needed rows etc.
Do you actually have any examples of this causing you a problem? As ever, beware premature optimization
Matt