Vamsi ... you have almost got it!
I still suggest starting with the simplest clock possible and see if clockDesign can meet your requirements.
Start with one drop, If not, try two, then three, then four........ no sense in making your life more complicated than it already is.
The only reason we required multiple clock drops was to reduce clock insertion latency on the high speed interface module to full custom ADC.
The ADC was 16mm tall and the interface module was pitch matched at 2mm x 16mm, we could not meet the maximum latency specification across the full 16mm distance.
We ended up requiring four clock drops, if I were to do this again I would request to have interface RTL coded into four separate self contained channels from the get go.
The layout would then be one module replicated four times , too easy.
One thing the RTL designers don't seem to comprehend is the importance of logical hierarchy.
An optimal logical hierarchy allows us to decide the optimal layout strategy in ... hmm ... layout.
Layout can choose to use or ignore logical hierarchy ( partition, region, guide, modulePadding etc etc etc )
Flatland RTL coding offers the layout team no options but to take one possibly very difficult route.
Sorry for the rant, I have to try and convince an RTL designers boss, that 1 man week re-coding / re-verifying will save me 4 weeks in layout.