is it worth supporting implicit rule target patterns as .ONESHELL dependencies?

In writing docs I noticed that some directive targets support implicit
rules patterns as dependencies (e.g. .NOTINTERMEDIATE) while others
don't (e.g. .NOTPARALLEL).

Would it be considered mandatory for e.g. .ONESHELL: %.o to be
supported?  Personally I never use implicit rules because static
pattern rules are just much less confusing generally, and it looks
like implicit rule pattern support will significantly complicate the
implementation.  Static pattern rules (with e.g. $(OBJS) as
dependencies of .ONESHELL and a corresponding static pattern rule)
work fine with what I already have.  It would probably be pretty easy
to arrange for an error message with a hint about what to do if
per-target .ONESHELL with patterns is desired (use a static pattern
rule).

Thoughts?