The non-guix repository and their substitute has you covered in the non-gnu side of things. You can use a regular kernel (read:not linix-libre) and it downloads all the required microcode and drivers.
1: And this is perfectly fine; communities can and should have such standards, but it will be off-putting to those who do not share the same values.
Guix is a known language scheme.
nix is off - I can't work out what parameters are needed for any one function call they all appear to be in a global namespace.
Unfortunately I need to be able to use non Linux systems
If you are talking about something you saw in the nixpkgs repo, then that is probably the callPackage design pattern [0], which is basically a form of automatic dependency injection.
It definitely made it hard for me to grok how nixpkgs package definitions worked at first - there was so much stuff getting injected dynamically, without any trace of where those dependencies lived.
The callPackage pattern is an important piece that allows you to override a dependency with a different version, though, which is essential when customizing existing packages for your own needs.
[0]: https://nixos.org/guides/nix-pills/callpackage-design-patter...
How files all each other and the parameters is odd. You call a function with two parameters but the file starts with many