Remove inactive Compute Scalar operators from the execution plan
When a Compute Scalar is in an execution plan, then depending on what exactly has to be computed, in many cases the computation is actually performed elsewhere (as described at https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms178082(v=sql.105)?redirectedfrom=MSDN) and the Compute Scalar does nothing anymore. This makes execution plans look more complex then they need to be, and when there's a bad cardinality estimate, the arrow width as rendered in Management Studio gets confusing.
Please add a post-processing step to the optimizer that looks at each Compute Scalar operator. If any of its computations will actually be done in another operator, then add the formula as a Defined Values property (and, if needed, the result column in the Output List property) of that operator, and remove the computation from the Compute Scalar. If no computations are left after this, remove the Compute Scalar completely.
The benefit will be that the execution plan shown to the user is a more accurate representation of how the query is actually executed, with less room for confusion.