Stacking patches is a potentially tricky activity, especially when they might play with the same things (the font and proper caser maybe being that, though it does say it was built with it in mind). Even when not if the hacks want some extra space to do their business in the hackers responsible might have chosen the same previously free bit of space.
One of those also notes it does not work on some hardware, which can also mean lesser emulators like those on phones and embedded hardware will not work (or conversely super accurate emulators might not work).
First thing might be.
Can you get the hacks individually working? That is to say 1 ROM, 1 hack, 3 ROMs then to test and make sure you have all those sorted as a first pass.
Bonus here is you can also then strip or add headers as you will to generate simple patches with all them expecting (or not expecting if you prefer) the header and thus not have to fiddle around removing and adding things between patches.
The entry on the page for the first and third (VFW and scroll) say the same ROM so assuming the page itself is correct then whatever you did for the variable font should do for the
If you have all three hacks confirmed as working individually then time to start stacking.
You can do the full combination of hacks and orders (sometimes the order in which you stack patches can make a difference, usually only when you are doing a patch that alters a patch but not always) if you really wanted but I would probably just start by applying one and then checking the others with it, and then doing it for the second and third. First, second and third is pretty arbitrary at this point so go with your order in the post above if you really want.
If you have the combinations of the two all doing things and working you can then get to three.
Next step is there are some tools that will attempt to detect "collisions" between patches. Normally I don't suggest people read too much into them but they can be useful as a first pass.