Is there a reason other than possibly choosing releases unsupported by rancher that the automated upgrades doc states you should not use your own system-upgrade-controller plans when you’re dealing with clusters imported into rancher?

Because rancher generates its own suc deployment and plans to manage versions

Should I avoid using my own system upgrade controller deployment at all when using rancher?

If you put the controller and plans in your own namespace you should be ok.