Either it's involuntary bad design, and the author should be warned.

(The right design is to only use Try::Tiny in the desired scope)

Or the author does exactly know why he's doing this and can easily disable the warning.

Considering that many projects are maintained by multiple authors, who often just C&P "working" code from former authors, this warning might be a good idea...

> which I politely called less simplified.

I politely called this "constructed"

The only probable "false positive" I see in reporting conflicts is by using feature "try" in a class/package also defining a method ->try() which is never called as a function.

But this warning would never be reported in my concept, because use feature normally happens long before subs are declared. Again: Pathological exceptions to that style imply that the author should actively disable the warning.