I think we may neew a few rules to cover this issue

When criteria: javaclass references="io.quarkus.qute.api.CheckedTemplate"
location: ANNOTATION

Category: Mandatory
SP: 1

Title: io.quarkus.qute.api.CheckedTemplate annotation should be replaced with io.quarkus.qute.CheckedTemplate
Message: The deprecated annotations from the io.quarkus.qute.api package were removed. All occurrences of @io.quarkus.qute.api.CheckedTemplate should be replaced with @io.quarkus.qute.CheckedTemplate. Checked templates require type-safe expressions by default, i.e. expressions that can be validated at build time. It's possible to use @CheckedTemplate(requireTypeSafeExpressions = false) to relax this requirement.

Quarkus - Migration Guide 2.0 link

----------------------------------------------------
When criteria: javaclass references="io.quarkus.qute.api.ResourcePath"
location: ANNOTATION

Category: Mandatory
SP: 1

Title:io.quarkus.qute.api.ResourcePath annotation should be replaced with io.quarkus.qute.Location.
Message: The deprecated annotations from the io.quarkus.qute.api package were removed. All occurrences of @io.quarkus.qute.api.ResourcePath should be replaced with @io.quarkus.qute.Location.

Quarkus - Migration Guide 2.0 link

------------------------------------------------------
We can have a rule that checks for an implementation of the NamespaceResolver interface.

When criteria: javaclass references="io.quarkus.qute.NamespaceResolver"
location: IMPLEMENTS_TYPE

Category: Information
SP: 0

Title: io.quarkus.qute.NamespaceResolver implementation
Message: Multiple NamespaceResolver instances can be registered for the same namespace provided that each declares a different priority.

Quarkus - Migration Guide 2.0 link