I think the issue you face could be side effect of one of the following things:
1. Most probably the association between Audit and User is set to IsManaged = true. As result Telerik Data Access will load the Audits collection fully when you try to add an entity in it. That could be the reason of the queries you observe. I suggest you to remove the IsManaged() call in your fluent mapping for this association.
2. It could be caused by a custom code that tries to reach all properties and thus the navigation property Audits gets loaded.
If non of the above help you then you could consider braking the physical association between both entities and manage it logically in your code.
I hope this information will help you to identify the root case.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.