None of the three is in strict; each is off unless you set it.
noUnusedLocals(TS6133 / TS6196 / TS6192): a local variable, function, class, type, interface, import, orprivatemember that is never read. Assigning to it doesn't count as use. Exports are never reported, since another file may use them.noUnusedParameters(TS6133): unread parameters, also destructured parameter parts and unused type parameters. A leading underscore (_req) exempts a parameter, which the tsconfig reference documents for parameters. In my tests it also exempted array-destructuring slots, but not an ordinary local such asconst _x.noFallthroughCasesInSwitch(TS7029): a non-emptycasewhose end is reachable, so control runs into the next clause. Empty cases (case 1: case 2:) are allowed for grouping. It uses control-flow reachability:break,return,throw,continue, or a call to a function returningneverall end a case.
Compiler or linter? These are errors: with them on, tsc exits non-zero and an unused variable you left while editing fails the type-check script. Emit still happens unless noEmitOnError is set. A linter rule can be a warning, autofixed, and configured (ignore patterns, rest siblings, a // falls through comment), and ESLint's core no-fallthrough accepts such a comment where TS7029 does not.
What I do: keep noFallthroughCasesInSwitch in tsconfig, since a silent fallthrough is a real bug and there is little to configure. Put unused-code checks in one place: the linter if the project has one (e.g. @typescript-eslint/no-unused-vars), otherwise the two compiler flags. Having both reports each problem twice.