If you really want to use Genesis /Genesis 2 content in Poser, you are much better off using the DSON Importer for Poser. That is what it is for, after all. 

You are missing the scope of the exercise. Doing things the canonical way is for wimps and slaves of the evil corporations; even worse, you end up with a success. Doing things in a convoluted and painful way, ending inevitably with a suboptimal result is the precondition to be able to reach the desired conclusion that the new technology is inferior to the good ol' ways.

No, you simply don't care for the results of my past few months experimenting with DSON - I have run genesis 1 & 2 with DSON and as an exported Poser-native figure.  No comparison - genesis figures in Poser performs better without DSON.

The performance of DSON nose-dives once you move beyond 1 figure.  Granted, if all you are doing is single figure images, it isn't too bad - load genesis, get a cup of coffee while the .obj is being built, rinse, lather, repeat for every .duf you select - the problem is when one moves beyond 1 fully clothed figure, it causes Poser to become crash prone and really slow. (And this is on an 8 core Mac Pro, not an i3 struggling by with 2Gb of ram.)

You see, EVERY .duf file has to go through the DSON subsystem. Not just the character, but every piece of clothing, every pose, every hair, everything.  The software simply isn't robust enough to handle anything beyond 1 fully clothed figure.  And since DAZ has changed course yet again, they will never spend any time on it to make it robust. Not that any of their software was ever anything to write home about in the first place.

It starts with how the genesis product is built - the base assumptions that DAZ started designing the genesis figure and DS 4 were thrown out by the time DS 4.0 was released.  By the time DAZ changed course with where the content you purchased would reside, the file formats were set - which led to some unfortunate 2nd and 3rd order effects.  For example:

The DSON subsystem in Poser will stuff everything it sees into a genesis figure - it is real easy to fire up DSON and end up with a 1Gb figure, before you add the first piece of hair, shoes, or clothes.  Which is why I had to spend so much time on how to structure a DS runtime to make it efficient in Poser.  I have found many, many ways how NOT to do it.  The number one way not to use genesis for instance is to have everything in 1 genesis runtime (i.e. use the DIM with all defaults) - that way leads to madness.

The solution is to build separate runtimes for each of your genesis 2 figures - this means editing your genesis 2 starter essential packages.  Of course there are also differing ways to do that.  One can build 1 base genesis 2 female runtime and keep all of your data/people files that are common in one and then in your separate sculpt runtimes just have your sculpt specific files separate.  Or one can make a separate sculpt runtime and have each one have both common & sculpt specific files - which means you only have to load that 1 runtime into Poser.

Then there is all of the clean-up that must be done after you have saved the genesis figure out.  Not to mention how DSON switches the UVs when you save a DSON genesis figure.  So far, the only way I have figured out how to save out a genesis 2 figure and keep the original UVs is by exporting the figure out of DS.

At the end of the day, you can certainly get a fairly robust figure that doesn't take up a lot of memory (I am able to keep mine around 20 - 40Mb).  The question is are the characters made by the handful of vendors that make content for genesis 2 on a regular basis worth the effort.  The genesis 2 life-cycle had a dozen or so sculpts (as Netherworks refers to them - Aiko 6, Mei Lin 6, Olympia 6, etc) and of those, they only have between 4 - 8 characters made for them.  This ties back into the cost-benefit analysis.  The genesis 2 line is significantly more expensive due to the sculpts, HD morphs and the paucity of actual characters made for them.

At the end of the day the genesis 1 and 2 figures can be used - but the Poser users has to have a good understanding of how the DSON system and the genesis figures work to get the best results.