Hoping for some help - I can't find this in the manuals...
 
Let's say I have one track, with a bunch of Effects in the FX Rack.
I want to "process" and Bounce that Track, so the Effects are rendered into the audio result, so that even if I were to delete the FX from the rack (and thus lighten the CPU Load), they would be heard in the rendered Audio.
 
Yeah, I know I wouldn't be able to adjust the FX later...
 
How does one do this, please?

You already answered you own question: Bounce to track is the most preferred (?) method, Freeze is another.
Also, Apply FX is possible, but not recommendable, because you'll lose the original track.
I read it you're not willing to use Bounce. If so, why?

Use the Freeze function. It renders the audio with the effects, shuts down the effects but saves them in case you want unfreeze later on. 

As others have said, use the freeze function. It looks like a snowflake icon on the track.

Now and then we've seen here threads about difficulties in thawing frozen tracks. That's why I prefer bouncing, especially, if the track in question  is somehow crucial and has required extra work.

If CPU hit is the primary concern, the counterpoint to bouncing a track(s) is to also archive the original(s). Archiving will remove the track from CPU processing, because it requires the transport to be stopped to undo it. Operations that can be done "on the fly" typically have some CPU overhead going on in anticipation of it being changed while the transport is running.
 
Another thing to bear in mind is that some operations can be "baked in" and totally forgotten about. Noise reduction is a good example... there is no reason to continually process every sample in a track each pass when the desired effect is "permanent."
 
To Kalle's other point above, I have also seen posts of VST(i)s losing presets when being unfrozen; so a side comment to that is if you spend a lot of time working in a VST(i), then save the work in that VST(i) to a preset before freezing. Use a descriptive name when doing so, since it might be years from now that you realize that you need to recall it (such as "[song name] [track type]").

Well, thanks, all! I will try both the Freeze and Bounce options under controlled circumstances.
 
In my experience, Bounce will "render" any clip gain and pan envelopes, but has NOT embedded the track's attached EFX. Is that a PEBCAK error on my part, or some sneaky little setting that I don't know about?
 
And I never thought of Freeze - I'll try it.
 
In both cases, my intent is to lock the track in place, in order to DropBox it to a collaborator across the country who is running Ableton: so I don't want either of our respective DAW's gumming-up my production values! :)

There are two bounces... "bounce to clip(s)" which you describe above, and "bounce to tracks(s)," which pops up a dialog with many options on it before doing. To lower CPU hit, you want to bounce to track(s) [highlight them and then select that in the "Tracks" menu at the top of the Track View]... when finished, Archive [the "A" button in the original track(s) you bounced]. This will bounce and also remove the track(s) you bounced from CPU usage (via the archiving).

Dibubba
 
In both cases, my intent is to lock the track in place, in order to DropBox it to a collaborator across the country who is running Ableton: so I don't want either of our respective DAW's gumming-up my production values! :)

In that case, should you not export it as broadcast wav? BWAV includes a timestamp to position the clip correctly.
You need to send an independent wav-file to your collaborator, not a SONAR project track. Or am I misunderstanding something? Ableton doesn't understand anything labelled SONAR.