The information in the .eso file is the same as that within the .CSVs that honeybee already parses. Am I correct in understanding that you just want this feature so that you can import results to honeybee from a simulation you ran from DesignBuilder? If so, I have a few suggestions. First, if you have DesignBuilder write out your IDF and you use the “Honeybee_Rerun IDF” component to execute the simulation, it will run the IDF in a manner that gives you the CSV derived from the ESO so honeybee can parse it in. Another option is to run the ReadVarEso function in that comes with E+ and pass in your DesignBuilder .eso file. This will convert the ESO to a CSV that honeybee can read.
Yet another option is, if DesignBuilder can output the E+ SQL file, all of the data in the ESO gets written into this SQL file. The most recent honeybee[+], which is under heavy development has a wide range of components to import data from this SQL. So this might be best longer-term solution if DesignBuilder produces the SQL.