tutorials
the tutorials are aimed at giving a hands on experience assuming no MIDI knowledge.
You will likely find the one on the MIDI monitor (SbS04?) useful as it shows how to make it a central tool in checking that your message flow is doing want you want
clock
If that’s all that you need to send out to FAMC|MP-201|Reflex|Gizmo then looks like you don’t need any A → A pipelines.
What you’ve just described would look a bit like this:
featuring:
-
Clock filtered out from A-IN (just in case any of FAMC|MP-201|Reflex pass it on!)
-
use of a Virtual I/O to send Clock to all outs (Virtual ports are a v. powerful MH feature)
-
label for Virtual C changed to aid readability
-
Virtual A-IN left trailing as a “To Be Continued…”
You’re likely to have at least one of these for each MIDI-OUT that you want FAMC|MP-201|Reflex to control. Each will probably have channel filters and the like
tap tempo
There is currently no Tap Tempo pipe or Tap Tempo property for Clock.
It’s come up perhaps surprisingly infrequently as a request. 
The key entry in this short list is @Giedrius here, saying
Tap Tempo is simply not implemented yet. How it could work is to provide a parameter that could be mapped (like “Manual Retrigger” in LFOs) that would react to taps and adjust the tempo.
Now, a number of long-time users are watching for the latest firmware update that it appears Giedrius is currently working on because it might include what promises be a revolution in mapping.
But apart(!) from that, G hasn’t given any indication of other new features
my guess, @jazzboxuz, is that the user base for Midihub when it started was skewed toward synthesists. Now, as the audience gets broader as Midihub’s reputation spreads, perhaps there’ll be more demand for functionality like tap tempo. Maybe Giedrius will include it in FW 1.14.x!