Construct follows the same API patterns as used by the browser (e.g. addEventListener). If we deviate from that I think it actually overall makes coding harder, as you have to learn different patterns, and remember which pattern fits to which feature. This kind of inconsistency annoys me regularly when using third-party libraries which deviate from the browser way of doing things (e.g. using on instead of addEventListener). It also reduces the use of Construct in education, as if your early coding is using the same patterns as industry-standard code, then you're already learning useful real-world skills instead of tool-specific details.
Still, there's nothing stopping anyone using the coding feature to write a library that does that kind of thing! You can always write code to "layer on top" a differently-designed API that works like you want.