Rhino and VisualArq work very well together and are useful on a variety of project sizes for varying uses. Of course, this is all based on my own experiences so others may have different ideas about the benefits and drawbacks. I’m referring only to the PC versions. I’m also assuming your end goal of a BIM software is to develop construction documents. In the future this may not necessarily be the case, but this is where we are at the moment.
I would say Rhino/VisualArq is a good standalone BIM software for smaller projects with fewer than say, 50 architectural sheets. For larger projects, it is very useful as a design/modeling tool which is later intergrated into a larger BIM software such as Revit.
I’m most familiar with Revit as the BIM application. Revit is great for data organization and repetitive buildings. It is terrible for design flexibility and small one-off projects. Revit is a beast, especially when it comes to schedules and working with very large and complicated projects. You can easily work on large projects with hundreds of sheets, and thousands of elements such as doors, plumbing fixtures, etc that would need to be referenced in a schedule. For large complicated buildings that have months or years of drawing time this is probably the construction document generation software for you. That said, it is painful to work outside of the boundaries that autodesk has established. You can find endless numbers of forums where people have complicated work-arounds for seemingly simple tasks that for whatever reason are not natively a part of Revit. The software updates generally do not resolve these workarounds so simple annoyances from 10 years ago are often still annoyances. The design method is not intuitive or flexible. Nearly every firm I’ve ever heard of uses some other modeling software and then imports or rebuilds the design in Revit later. Autodesk is essentially a monopoly and the pricing of Revit reflects that. This is not as big a deal for mid and large size firms but can be a major impediment to smaller ones. There is no backward compatibility, no ability to work with other versions even between consultants, and it is the most expensive architectural software I see commonly used (not counting Ghery Tech, Catia, and such). That being said, I would not want to generate construction documents on a massive project with anything else.
Rhino is, in my opinion, currently the best architectural modeling software out there. It’s flexible for a variety of workflows, has great support from the developer, and has a lot of tremendous plugins. Visualarq gives it a lot of added power and makes it much more architectural than simply modeling forms. You can create floor plans, elevations, sections, (though unfortunately no reflected ceiling plans) etc as well as create schedules for the doors, fixtures, etc. If you are familiar with grasshopper it is a big plus in automating a lot of otherwise tedious operations. The functionality is good for a small set of construction documents or ones that will be creates in weeks/months rather than months/years. For larger projects, the IFC plugin functionality makes moving slabs, walls, doors, columns, etc from Rhino into Revit much more seamless. You can create initial design massings and corresponding plans in Rhino/VA, and then move them into Revit for more documentation and less general design studies. The community for both Rhino and Visualarq is very supportive and it is not uncommon for other users and/or developers from McNeel and Asuni to regularly provide input and help on questions.
I hope that helps.