Suggestion: new sniff to detect code inefficiencies

What's the general opinion on having a sniff to detect the following type of code patterns and throw warnings when detected ? Useful or not ?

echo sprintf( 'string %s', 'replacement'); // Should use `printf()` instead.
echo esc_html__( 'string', 'domain' ); // Should use `esc_html_e()` instead.
echo selected( $selected, $current, false ); // Should use `selected( $selected, $current )` instead.
echo get_search_form( false ); // Should use `get_search_form()` instead.

Of course, it would need to be verified that such a call is not followed by a concatenation adding more text, but that shouldn't be too hard to do.

echo sprintf( 'string %s', 'replacement') . 'something else'; // This is fine.

For a list of functions which have a $echo = true toggle as one of the parameters, Google Search will probably work better than the wp.org search.

Oh... and if you like the idea, more examples of code patterns to listen for would be welcome!

Review the proposed echo-related patterns and the examples in the issue, including cases with and without concatenation. Define which patterns and additional examples should be supported before identifying the implementation files and tests.