So... I tried to look this up starting from one of my working setups, a OpenWRT device, and what did I find there? I found they are using a patched wpa_supplicant which says:
-H = connect to a hostapd instance to manage state changes
Well, here is my setup which seems to work OK on my Debian Jessie.
I'll be using hostapd and dnsmasq, what I do is disable them so that they are not started on boot and I start them whenever I need them (use update-rc.d for this or any other method you like).
I have defined an interface (ap0) which is not automatic or hotplug and which I ifup manually when I want to repeat a wifi:
The /etc/hostapd/hostapd.conf.nochannel file is a simple config file, something like this works:
Hope you find this usefull, and if you want to enlighten the -H parameter history feel free to comment.
What I think after reading the commit (https://dev.openwrt.org/browser/trunk/package/network/services/hostapd/patches/453-ap_sta_support.patch?rev=37738) is that they are having wpa_supplicant reload any time the client reconnects or whatever, but this can also be done on wpa_cli, so that must be why it hasn't reached upstream (but that's just what I'm guessing, any light out there?).
It feels nice to write after such a long time :-) Regards.