By default, the score is the per-bin average of whatever is in the
bigWig file. If that's "read coverage" or "fragment coverage" then
that's the score. If the bigWig files contain log2 fold-changes vs.
input then that's the score.
I assume that your second question pertains to the bin size setting in
computeMatrix. This effectively sets its resolution and, thus, the size
of the file it produces. This is convenient since it allows you to
produce images with multiple data resolutions. You are, of course,
limited by the resolution of the underlying bigWig files, but since in
the profiles (e.g., from plotProfile or the top of the default
plotHeatmap output) you're averaging over a typically huge number of
regions, a relatively coarse resolution in the bigWig files stills
allows for good signal resolution in the resulting plots.
Clustering is applied to all samples at once. Relatedly, all samples
will always be identically sorted, so if you make a heatmap you can be
confident that a given row in one sample came from the same region as
the same rows in other samples.
Devon