"Consider whether the performance impact of registering in the container and resolving instances from it is acceptable in your scenario. For example, if you need to create 10,000 polygons to draw a surface within the local scope of a rendering method, the cost of resolving all of those polygon instances through the container might have a significant performance cost because of the container's use of reflection for creating each entity."
Please see the section title, "Considerations for Using the Container", in the following link:
One possible solution is not to resolve/inject the module containing your rendering method inside the Unity Container.
You folks at Telerik may want to take a closer look at this, perhaps do a mockup to test this out, given that Unity is being use for a great many projects.