You have a few options. First, don't allow the master instance to simply start on it's own.
Second, depending in your particular scenario and requirements you could have the slave write the AOF to a shared file system or run the slave on te same node. Then, you could have the config file enable AOF and read from where te file is stored.
Then your start process is something like:
1) start redis with AOF
2) when done reading it, your monitor script disables AOF using the config set command.
This assumes AOF can be changed via the coding set command - I'm not by a system I can test with.
If it can't, then you would instead need to alter the master/slave relationship on master start so it syncs the data from the slave. This would also be a custom setup but not too tricky.