Alright, updated then, then I'll update the description.

I'm not sure if a "*.cfg" file inside the vpk can be loaded automatically. But at least if you put that "aim.cfg" in the vpk, people can take a look into the "aim.cfg" so they can copy-paste the "aim.cfg" or simply just the alias settings to their own cfg files.

Yeah, true. Will having the aim.cfg in the vpk allow it to be targeted by keybinds?

After checking what's inside the vpk file, probably you can also put the cfg file that already has your alias settings on your guide, in case if there's anyone who has difficulty in following each step on your guide. Most people usually know how to change key binds, so if there's a cfg file with your alias settings in it, they'll only need to change the keybinds in case if they want to use other keys.

I also recommend using 1/2 of whatever your current playermodel and weapon FOV is, so that you get a good zoom.