In a couple of projects we have used sitefinity installations as web application projects -> precompiled.
We have had good experiences with do that. Sometimes even seen performance increases over a non precompiled version especially on sub pages that are not frequently visited (think of all the sitefinity backed sub pages that are usually visited only a few times, they suddenly just appear without any loading time).
After a redeployment you should definitely trigger a page load yourself since the first time it has to load the assembly, rather than just the requested page and you don't want any of your users to experience that loading time.
There a couple of guides how to convert sitefinty to a web application that can be precompiled. I have found that this one is the most accurate one and even has a backreference to older versions:
Installing Sitefinity as a Web Application in Visual Studio: