Hello. Welcome to the world of TAS'ing. I am relatively new too so don't take all of this as gospel but here is what I can answer for you.
First off, there is already a forum topic for NES Jurassic Park posted
here. jlun2 currently is working on a run of this game as well, but hasn't posted a WIP for about 4 months. He is very active on the site so if you wanted to continue on this movie and posted in that thread I am sure he would help you if you had questions. Up to the point that you end the movie he is around 650 frames, about 11 seconds, ahead.
Now for your other questions:
You find glitches just through experimentation and trying to find ways to get the movie to end faster. Not every game has obvious glitches, and in many cases the glitches do not improve the movie.
I also use fceux 2.1.6 and as it is not released they haven't released the documentation yet. It has an expected release any week now and when it is officially released the documentation will be included. There isn't really a tool that speeds up the process any faster than TAS Editor can. It really is about trying varying strategies until you find the fastest path.
To find memory addresses you use Ram Search and Ram Watch listed under the tools header in fceux. How to use this portion of the program can be found
here.
That is a basic definition of luck manipulation, meaning that it is doing things slightly different to get more favorable results. A more thorough definition can be found
here.
There isn't a way to necessarily view the things that are off screen but you can keep track of these details through the ram watch and if you really want to try you can get into
lua scripting which can help display pertinent information on screen.
Good luck with TAS'ing and even though you are a little behind just keep trying. My first movie attempt ended up being about 15 minutes slower than a current run but I have gotten better.