Welcome! I don't think the Sublime developers will change the plugin API dramatically at this point (@ben-schaaf is in this thread; we can ask him :) So, old plugins should remain compatible. What we should be concerned about is that if something new is invented, it will probably appear in a more widespread editors first. However, as practice shows, new plugins for Sublime continue to be created[1] so we are not missing lot.
In the argument of Sublime Text vs. VS Code, the deal breaker for me has always been VS Code telemetry. Of course, you can disable it in the settings or firewall, but then you have to constantly monitor it to ensure that some "bug" or "update" does not re-enable it back. Alternatively, you can choose not to care about potentially sharing everything with Microsoft and their 829+ partners. However, I prefer to pay for Sublime rather than participate in some manager's brilliant idea to extract revenue from a "free" user base.
Using Sublime Text since version 2, one of my relatively recent discoveries has been the Markdown Images Plugin[1], which renders images inline (rather than in a separate preview, as other editors do).
I find it extremely convenient to include images alongside text, such as diagrams and schematics for work, photos of goods in a shopping list, and inspiration collections for hobby projects, etc.
When combined with a simple web clipper script[2], it has been a game changer for me.