Remarks

The value passed as the text parameter can be in any of the constant, number, date, or time formats recognized by DAX. If text is not in one of these formats, an error is returned.

VALUE is not common because DAX implicitly converts text to numbers as necessary.

VALUE raises an error if the conversion is not possible. In case VALUE is executed iterating a column that might contain invalid values, filtering the table may not be enough because the Vertipaq Engine that does not that VALUE is called after applying the filter. To guarantee VALUE is called for valid values, there should be an IF statement to protect the code.
For example, the following two examples might raise an error:

SUMX ( 
    FILTER (
        'Data',
        'Data'[Type] = "Number"
    ),
    VALUE ( 'Data'[Value] )
)

CALCULATE (
   SUMX ( 
        'Data',
        VALUE ( 'Data'[Value] )
    ),
    'Data'[Type] = "Number"
)

A safe version of the two previous examples is the following:

SUMX ( 
    FILTER (
        'Data',
        'Data'[Type] = "Number"
    ),
    IF ( 
        'Data'[Type] = "Number",
        VALUE ( 'Data'[Value] )
    )
)

CALCULATE (
   SUMX ( 
        'Data',
        IF ( 
            'Data'[Type] = "Number",
            VALUE ( 'Data'[Value] )
        )
    ),
    'Data'[Type] = "Number"
)

Aggregation expressions should not assume that the filter is applied first; instead, they should ensure their own safety during execution.
This does not implies that aggregation expressions will be evaluated during execution while ignoring the filter, which would be a performance concern.
However, the VALUE expression may be evaluated during the Vertipaq Engine’s preparation phase against some values without the filter being applied.