... the alternate {alternatIVe} ways of solving this problem.
Note that we have two "problems" : the one you defined
really --as pointed out by DDK-- was to secure the extant,
"preconfigured"
Dines knot;but some us *backed-up* to the problem that the
Dines knotwas trying to solve, and offered alternatives to that. (Imagine
an instruction : "First, UNtie the preconfigured knot; THEN ..." ! )

So far, the data I'm collected suggests that the buntline hitch on its own won't do the trick;
But please note that what Roo presented was NOT exactly
the
buntline hitch, but was that structure modified by taking
the noose's standing part through the knot a 2nd time.
Are you saying that
this revised structure doesn't work?
DDK mentioned that the post goes around the object and then pre-tied loops come over it at the end - that's exactly how this system works.
Okay, I wanted a more detailed explanation of the knotting
situation. The provided diagram above shows a relatively
large (green-shaded) "object" for the line, suggesting that
the
buntline hitch indeed will have some challenges, with
the ultimately loaded lines pulling it apart --and that perhaps
the
two half-hitches orientation of the
clove hitch would
better serve, here (with Roo's modification).
And to the question of exactly how this knotting/binding
is effected, let me point out that in some case what we
are facing is some
fixed amount of slippage/yield from
the knot, which serves to lengthen-loosen the binding loop;
but were one to make a
double loop, the fixed yield
would be divided in half in its loosening effect (half to each
of the two loops. So, without adjusting any of the knots
--assuming that they do lock and hold, but just yield some
tightness in doing so--, one can halve the effect on the binding.
(in theory)
--dl*
====