Looks great, and a great explanation of why this is useful. Thanks!

This blog post should also probably mention the new verbatimModuleSyntax compiler option (and why you might not want to use it).

We also might want to wait for this new rule before publishing this:
#6382
Which would help explain to people what they can do about the footgun in verbatimModuleSyntax.

We also probably want to include mention of other rules that help ensure consistency in your imports:

• import/consistent-type-specifier-style which will enforce consistent use of top-level vs inline type qualifier
• import/no-duplicates which will warn against unnecessary duplicate imports (and with the inline-type-imports option can work in tandem with the above rule).

In conjunction with consistent-type-imports, the rules can enforce your imports are always properly qualified and are written in a standard, predictable style (eg always top-level type qualifier or always inline type-qualifier).

Frankly, I'd be much more interested in knowing how import type and import { type } play with each other and everything else. But I get they are probably not in scope of these rules anyway. We could wait for verbatimModuleSyntax before writing a follow-up post about all the different type import syntaxes.

this LGTM - there's lots of good content in there!