Underfire, the illustrations were provided to allow fellow pilot to e what they may not have seen before when considering how departure procedures are defined.
You are correct that an EO does no take these into account, merely terrain clearance requirements. For best vertical gains straight out departures are usually considered to best as the aircraft does not limb as well during a turn, in case of EO may no even limb at all in a turn.
EO procedures clear obstacles and terrain by minimum requirements underneath the considered flight path, whilst attempting simplicity or pilots as their workload is already high enough at these times.
Coded Eo procedures are commonly not possible as the FMC data is refreshed and loaded each 28 days, in line with AIRINC cycles, but EO procedures are type/operator specific and can only be loaded inoto FMC using Supplementary database, something that needs creating/monitoring/updating/installing/maintaining etc, some operators do not or can not spend resources on that. Granted, coded EO procedures would be better provided the aircraft can fly them (limiting bank angels, re-executing a new FMC selection of route, etc etc)