It's a team effort, totally, but I'm not going to put myself in a crap situation for you anymore than you are going to cover up a blatant TFR bust for me.
There is no covering up a TFR bust. Heck, if an altitude bust causes an RA or other evasive maneuver, there is no covering that up either.
Thanks, I totally understand that the controller was busy and that is likely why they told me to hold. And in all honestly I am still fairly new with using flight following.
It's no sweat. It happens. I wasn't there, and I don't have audio or radar playback, so I can't begin to speculate what the controller was or was not doing. I'm not perfect either, so I won't play "Mr. Perfect" by saying the controller should or should not have done something. From your recount, it sounded like an unusual situation that you handled perfectly well. It also sounded like the controller realized what you were asking for, and got to you quickly (as you said in your OP).
I think you have a good mentality for navigating the NAS. Remember, we are here for you; you keep us in business. Not the other way around.
In my facility, there was a national training refresher item about VFR flight following, and the services we provide. That's why this is all fresh in my mind
Inside controlled airspace, I can AND DO vector VFR aircraft if I feel either the aircraft's safety may be in jeopardy otherwise, or if I feel an operational advantage may be gained. I have also issued, and will continue to issue altitudes to VFR aircraft as well. Such as, "fly heading 170 and maintain VFR at or below 2,000. Traffic will be opposite direction over the shore VFR at 2,500."
Though the VFR/VFR or VFR/IFR separation requirements are negligible in controlled airspace, we still have a responsibility of aircraft separation and of providing a service. That does include vectors and altitude assignments if necessary for safety, or if we can obtain an operational advantage from it.