Yes, backwards compatibility for tooling, such as eslint, is the main reason to include both "exports" & "main" rules.

If both rules are included, the "exports" rules takes precedence for tooling that supports it, according to the npm docs that OP linked to, so there's no reason not to include both if backwards compatibility can be maintained.