I am not from the SimScale Team but the mentioned reasons for adding this feature is not a good one. In general, for CFD and actually for OpenFOAM this is not a big deal and I guess SimScale could implement this feature. However, I don’t know the software architecture which is behind and thus, the implementation could be a bit more challenging but making less mistakes would be not a good point. If you set some BC wrong, the solver will blow up fast. Okay there are the cases when users set up a set of boundary conditions which will lead to an numerical solution (Ax=b) but with an arbitrary number of possibilities. I am not sure if such a feature could provide the necessary information for unskilled people. In addition, I think SimScale applies appropriate or default BC if the user forgot some of them because no BC no numerical solution, no solving. In addition, you should specify which kind of quantity you would like to monitor? An averaged value, or something else. Keep in mind that slicing etc, will always induce errors and other stuff and averaging as an own topic. Area averaging, volume averaging (but with a slice?) and so on
I just wanted to make some more statements. In general I guess it is nice to have especially for faster post-processing like - run-time processing. But there are so many possibilities with FOAM.