Ripit:
I think I understand your question and hopefully I can give you what my 2 cents would be. We also use Nexus and currently have the Nexus Import, Processor and Rip modules. For most of our jobs we also use a Raster, Trap, Link workflow that produces CT/LW and the associated EPS link file that can be used as you said for proofs, plates, etc. or as most people refer to as a ROOM (rip once output many) workflow. While this works great and you can view the results of the ripped file using Insight, when you talk about a Normalized PDF workflow it gets a little different.
Not sure if you use Artpro or not but we do for any job that has complex transparencies etc; using Artpro is sort of like a Normalized PDF workflow in that once you import your files into Artpro, trap them etc etc. you can view them in Artpro and once you are happy, you still have to send them thru the rip for output to proof, plate etc. While your final output should be the same and is 98 to 99% of the time, it is sort of a leap of faith in that what you are looking at in Artpro will look the same once it goes thru the rip to make the OPPO and link file.
A normalized PDF workflow would be similar in that you would process whatever art you get in ( Indesign, Quark, AI etc.) and convert into a PDF. You could then take that PDF and run it thru the AWS Total Rip and it will normalize it, and you can even run it thru their PDF trapper (similar to 4-stage vector as in Processor Module)
and once it is processed it would spit out the normalized PDF that would include traps etc. if they were applied. You could then take this PdF and send it to customers or approval (given it was small enough to email or post to FTP etc.) or you would run back thru the Total PDF rip for plates, proofs etc. and the output should be the same as you viewed the normalized PdF in say Acrobat or Neo etc.
Now when it comes to imposition it is a little different, where with your current WF you are taking the EPS link that was created and placing it into Preps, Dynastrip or even Powerlayout or Powerstepper and then writing PS and feeding back thru the Nexus rip to do the swap and then ouptput to plate, proof etc.
Using a Normalized PDF workflow you would actually place that normalized PDF into your impo program and then you would export out JDF and run that back thru your Nexus Total Rip (can you say no more page paths!!) and the rip would then do all the work of using the Normalized PdF and converting to 1bit Tiff or DCS etc. for output. This is where that leap of faith comes in again, as your final output should look the same and probably will 98 to 99% of the time.
Hope this helps out a little, a normalized PdF workflow is definitely the way of the future and has lots of benefits.
-Dub