Do you want to maintain another SVN repo in parallel to the SF one, why?
I vote for Apache configuration using WebDAV, because this is the most flexible solution IMHO. We have it running (but without using SSL) and the configuration was not complicated at all. We also use restricted repo access through authentication and WebSVN that enables repo browsing.
Maybe it is a good approach to first setup the simpler svn server and afterwards, if need arises, enable access via WebDAV.
But does this topic mean that you want to use the SVN repo as a replacement to UVS repo? That would mean your quick fixes and improvements would only be available there at first until someone (I think Max) synchronizes it with SF repo?
Why don't you want to use the trunk path or another additional path within the SF repo?