This rule would be beneficial to allow users to get the benefits of unicorn/better-regex without interfering with the regexp/strict rule from the eslint-plugin-regexp project.

Fail

const demo = /\}\{/ // Flagged by unicorn/better-regex if it has the unnecessary escape characters - and by `regexp/strict` if it doesn't.

Pass

Pass would be leaving the code untouched and without warning, as strict mode encourages including the escape characters. This also has the benefit of improving syntax highlighting, as the { and } are clearly highlighted as characters to match, as opposed to being highlighted as quantifiers.

const demo = /\}\{/ // Same code, just don't warn