@Thibault_Squarp , something i forgot to mention on my bug report…
I have play pad = play/pause… to ensure that some how the MIDI START/CONTINUE was not somehow being influence by how the PLAY button is handled.
btw: but a bit unrelated… if the clock timeout is ‘activated’, I think the play button should respect the play pad (play/pause) setting… and not force a reset.
EDIT 1: DAW notes:
Ableton Live (10) , I cannot find a way to force it to send midi clock when transport is stopped
Bitwig 3.0 - works perfectly.
Bitwig sends clock when transport is stopped, and indeed proves my hypothesis is correct. the continue functionality works perfectly.
(this is why Ive not noticed bug before, as this recently is the daw i mainly use)
so my current tip is for everyone to move to BWS, go on, you know you want to 
Logic Pro X 10.5, I cannot find a way to force it to send midi clock when transport is stopped.
(hands up, Im not that familiar with logic, though usually can find my way around!)
EDIT 2: Other daws I use
Cubase 9: works perfectly
option to send clock on stop, just dont check ‘always start/stop’ ;
Reason 10: works perfectly
it has option to send clock on stop
Renoise : not relevant
does not support continue.
Renoise - sends clock on transport STOP, but renoise doesn’t (appear to ) support MIDI CLOCK CONTINUE - a rather odd omission.
EDIT 3 : SUMMARY
it appears Logic and Ableton are the odd ones out here… most others DAWs give the option (or hard coded) to send clock when the transport is stopped.
that said, they are two of the most popular DAW, so kind of set their own standard!