It doesn't matter what's in the guts of the ASCOM driver if the mount
hardware, your NexStar 8SE in this case, does not support the commands
in its serial command protocol to effect the movements that pulse
guiding demands. The fact that pulse guiding is available when using the
driver with unrelated mount models such as the AVX is of no matter. The
driver either interrogates the mount hardware upon connecting to it to
ascertain its capabilities, or the ASCOM driver maintains a capabilities
table of mount models and firmware revisions. Either of which would
inform how it advertises the various ASCOM capabilities, pulse guiding
included.
To my knowledge, the only way to guide the NexStar series is via
old-fashioned ST4. This is where you physically connect the guide camera
directly to the mount via the "telephone" cable with the RJ12 6-pin
modular connectors. PHD2 sends guide corrections to the mount via the
camera, which basically acts as a relay and ST4 interface for your
computer. You will want to have PHD2 calibrate following every major
slew. The NextStar series are geared towards visual observing and
novice, no-frills imaging. It doesn't surprise me that it's not capable
of pulse guiding via its ASCOM driver.