Here's my take on this. The hold depicted in the attached procedure is a missed approach hold. I seriously doubt ATC would stack people in THAT hold waiting for THAT approach into THAT airport.
You might be surprised. Last year, I was going into Lawrence MA (KLWM) for the VOR 23 approach (
http://204.108.4.16/d-tpp/0811/00654VG23.PDF). There was someone else on the approach ahead, so Boston says, "Hold at Lawrence VOR as published." As you can see from the chart for that approach, there's no published hold at LWM VOR on that chart. We check the L-chart -- no published hold at LWM VOR there either. "Boston, Beech 123, there's no published hold at Lawrence VOR." "Beech 123, yes, there is -- I've got it on my scope." "Well, Boston, it's not on the approach chart and it's not on the enroute chart, so you'll have to read it to us." "Hold northeast of Lawrence on the 057 radial, right turns, EFC 1234."
While my trainee is going around in the hold, I look further -- guess what I find -- the ILS 05 approach (
http://204.108.4.16/d-tpp/0811/00654I5.PDF) has a published missed approach hold at the LWM VOR -- northeast, 057 radial, right turns. Not on the other approach charts, not on the L-chart.
So, be aware that any published hold is going to be depicted on the controller's scope, but the controller will not know where it's actually published -- the enroute ("L") chart, one or all of the approach charts, missed approach hold, HPILPT, whatever. But since it's on the scope, it may get used. So be prepared to go on a search-and-find expedition through your charts any time a controller says "hold as published" -- or be prepared to say, "I can't find it, request instructions."