Niels, you are correct that there are few examples of architecture for Maverick. I've done quite a lot of them for my clients. I've also acquired quite a few outdoor scenes made with Maverick.
Here's one quick example of an architectural scene. Maybe the image size here is too small to make out the spice jars inside the alcove on the right. But, this simple scene has well over a hundred objects in it - all textured with *sbsars, rather than with conventional shaders or texture maps. The original larger-size render required just about one hour to render in Maverick. It required two further minutes to render in Maxwell, and I think I got about the same quality.
Here is a Maxwell version with slightly different lighting, camera focal point, fewer objects, and maybe a very slight difference in the camera position.
So, I like Maverick for tons of things. But, the hitch is that any purely-GPU based rendering engine is going to slow-down a LOT when the scene contains hundreds of objects. I use both Maverick and Maxwell regularly, because when it comes to a complex architectural scene with lots and lots of objects, CPU rendering with a full deck of memory sticks is better than GPU rendering. This seems to be true, even when you're sporting one of the big nVidia cards. I believe that most professionals know this - that is, that purely GPU rendering engines lose their competative advantage over engines that use CPU's or can use both, like Maxwell, when it comes to scenes with hundreds of objects.