Hi Charles,
A few thoughts from me; Chris may have more to add.
1. An EG project is actually a ZIP file underneath it all. You could extract the underlying code by renaming the file with a .zip extension (I'd probably create a backup copy first!), unzipping it, then accessing the code in separate folders. I don't know if this is more automated than doing an Export all code manually. More details on the zip file details here:
http://support.sas.com/kb/18/414.html
2. I don't know of a specific way to chain multiple projects together. You can always create code templates from the tasks in question, save the code files, and then use %include on the code. You can also create multiple process flows and ordered lists as a way within a single project to easily control what executes. Usually, %include statements are used to either submit code at the beginning of using SAS or to bring in a specific chunk of pre-written code when needed. You can tackle the "code at the beginning" part in EG 4.2 by using Tools / Options / SAS Programs / Submit SAS code when server is connected. Bringing in a specific chunk or pre-written code can be applied to tasks as previously mentioned by creating code templates from those and saving the code.