I don't think you can do it without closing VS. However, I am not familiar with the domain structure of the VS application; theoretically speaking, it could be possible, but would create a performance and redundant complexity problem: working through the domain wall is inherently complex and involves IPC-like communication, because Application Domains are isolated from each other, pretty much like processes; they work in separate address spaces. So, if I was the architect of the Visual Studio, I would not add this complexity, because reloading Visual Studio would be a reasonable solution. Note that, in same cases, Visual Studio is unloaded and then automatically restarted. This is very indicative.
See also:
http://msdn.microsoft.com/en-us/library/yb506139%28v=vs.110%29.aspx[
^],
http://msdn.microsoft.com/en-us/library/system.appdomain.aspx[
^].
So, sorry for not 100% complete and not 100% certain solution. I cannot say "I am sure: replacing of the add-in implementation without reloading of Visual Studio is totally impossible". I can only say: in my opinion, this feature is highly unlikely. I really advise you not trying to achieve that. Unloading Visual Studio and loading it again is not a great burden you would put on your users.
—SA