Whilst I am most confident the Cameo implementation for SysMLv2 will become very feature rich and powerful, as it currently stands I would not quite recommend it yet for use on industrial strength projects unless you are a larger organisation with a large R&D department and can absorb the time it will take for some of the tool feature shortcomings to be addressed and you can spend sponsored time reporting bugs and issues. You should also already have trained staff with experience with SysMLv2, or engage an expert SysML/MBSE consultancy like Webel IT Australia.
And you'll need a lot of patience! Many essential aspects required for practical MBSE do not yet have convenient graphical feature support, and you'll have to know your SysMLv2 textual representation modelling code (which is a good idea anyway) and use the textual representation editor a lot.
The Cameo SysMLv2 Plugin understandably also does not yet have all of the wider MBSE ecosystem features of Cameo for SysMLv1.
My tentative recommendation for smaller organisations for now is to still use the tried and tested SysMLv1 in Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) with its wider ecosystem of supporting features and then rely later on the SysMLv1 to SysMLv2 conversion support (whilst perhaps becoming familiar with the SysMLv2 language in an exploratory spirit as a side-project). Unless, that is, you wish to invest long term in SysMLv2 from the start.
However, if your team is composed primarily of experienced programmers (coders) that could tilt your decision heavily in favour of already adopting SysMLv2 and the Cameo SysMLv2 Plugin and the Cameo SysMLv2 Evaluation Plugin, and they would likely also be able to handle creation of custom query view tables (which currently does not have sufficient graphical support), which are critical for communication with other stakeholders who are not familiar with SysMLv2 notation.