Hi there @kristianbrasel
As you said, collection-level pre-request scripts will execute prior to every request in the collection. Similarly, you could run your scripts at the folder- or request-level. This controls your scope a bit, but it’s still not accessible “globally”.
It’s not quite recommended, however you can also save your function as a variable (global, environment, collection, or whatever scope you choose). And then eval() it when needed. This gives you a little more flexibility to control your scope and allows you to share with team members if you wanted to. For example, global variables are available within a workspace. Environment variables are portable across collections. And so on.
If none of this is quite what you’re looking for, feel free to chime in on feature requests with specifics of your use case, like this.