best way to reuse the code from an existing rule?

[prescriptionlifeline]

Rector\Renaming\Rector\MethodCall\RenameMethodRector does 90% of what I'm wanting but I want it to change $someObject->oldMethod(); to SomeExampleClass::newMethod() and it doesn't look like I can do that with that rector or any other for that matter.

That said, I can hack RenameMethodRector up to do what I want. Like I can modify the refactorMethodCallAndStaticCall method so that after this line:

            $call->name = new Identifier($methodCallRename->getNewMethod());
            if ($methodCallRename instanceof MethodCallRenameWithArrayKey) {
                return new ArrayDimFetch($call, BuilderHelpers::normalizeValue($methodCallRename->getArrayKey()));
            }

It does this:

return new \PhpParser\Node\Expr\StaticCall(
   new \PhpParser\Node\Name\FullyQualified('SomeExampleClass'), 'newMethod', $call->args
);

That does the trick, however, I don't want to modify files in the vendor/ directory for obvious reasons.

I could copy / paste the contents of RenameMethodRector to a new file and hack the new file up but I'd also prefer not to do that. Like there's a lot of logic in RenameMethodRector that it'd be redundant to duplicate.

I can't extent RenameMethodRector and implement refactorMethodCallAndStaticCall to call parent::refactorMethodCallAndStaticCall() because (1) that method is private and (2) RenameMethodRector is a final class, meaning it can't be extended (although this does beg the question, why is the class final? what problems did y'all encounter that making that class final solved? if there were no such problems then maybe y'all could remove the final keyword?)

Another thing that occurred to me is that maybe I could implement RenameMethodRector in a new class. eg.

    public function __construct(ClassManipulator $classManipulator, ReflectionResolver $reflectionResolver, ReflectionProvider $reflectionProvider)
    {
        $this->renameMethodRector = new RenameMethodRector($classManipulator, $reflectionResolver, $reflectionProvider);
        $this->renameMethodRector->configure([
            new MethodCallRename('SomeExampleClass', 'oldMethod', 'newMethod'),
        ]);
    }

That gets problematic, however, because I then need to redefine autowire and the other public methods from AbstractRector. Like ideally I'd like future proof code and if I just had a from scratch Rector rule new parameters being added to the autowire method in AbstractRector wouldn't be an issue, but if I redefine it then I'd have to simultaneously make that same change in AbstractRector and then my implementation would only work on the newest version of Rector. And even then, if I'm extended AbstractRector I can't implement the enterNode method because that method is declared final in AbstractRector.

Implementing RectorInterface could work but then, at that point, I'd have to copy all the methods as AbstractRector implemented them, and half my goal here is to re-use code - not copy / cast large chunks of code.

My questions are twofold:

1. Is there another more elegant way to re-use the code that's in existing rules?
2. Why are all the rules declared final?