Depends. It’s dictated by how the code is structured. Also, it’s at the discretion of the author porting the code how much granularity (no pun intended) is desired.
Jumping in blind here, but a quick glance at the at the Clouds code shows that there seems to be a handful of self-contained components including the granulator, a looper, a WSOLA sampler, a phase vocoder, a correlator, a reverberator, and a pitch shifter. All bits that could potentially be mixed and matched in new an interesting ways. Some rain and sunshine to go with your clouds.
Those components do break down into lower levels. The Reverb, for instance, breaks down into delay line components, which are then used as delays and allpass filters in the reverb topology. These come with the reverb code one way or another. You could also port these as well. BUT, from a creative audio-programming standpoint, it’s probably not really worth breaking the reverb algorithm up.