Also, more events is not obligatory a bad thing, if done right, for starters, one could think the number of events is a direct representation of performances, and that would be completely wrong, as the number of events is for the entire project, not for every single layout, and due to how event works, it is more than likely that if you code the right way (avoiding unnessecary work for the browser), the events really have an impact only when they are needed.
also, always prioritize in that order:
-organisation, first, never think "yeah, even if it is badly written, that is fine", and NEVER EVER think "if I organise it I might lose performances". Groups, Includes, functions, global and local variables, all neat tools you have at your disposal can help in some case.
-flexibility: can you make some parts of your code more flexible? if so, you should try, that may really helps in the long run
-use features, they are here for that, but don't overdo it. Sometimes I see people using features just for the sake of using them even when this is not the case where it is meant to be used (I will not talk about "lerping movement" again, but keep in mind that if a feature does what you want, use it, however if it is not it is meant to be used for, either do not use it or add a comment to be sure someone can read it correctly).
-reduce redundant code, functions and families are great for that for instance (might not reduce the actual number of events, but at least it will be cleaner).
-and last:performances, performanes should always be your last concern, you can optimise clean code every time you want, but dirty code is unusable.