Torque Heatmap is a variation of CARTO Torque map and it shows the density of the points. The CARTO Torque map is an aggregator, it takes the range at time from your first date to your last date as one unit
Torque Heatmap is a variation of CARTO Torque map and it shows the density of the points. The CARTO Torque map is an aggregator, it takes the range at time from your first date to your last date as one unit, then it breaks them into smaller buckets/pieces/classes of time.
The number of buckets depends on the number of steps that you choose in the wizard/CartoCSS.
Torque is also a spatial aggregator, it's going to render an animation point representing a cluster of your dataset points. So when a user is looking at your map it wouldn't necessarily see points at the exact coordinates in your dataset like they would do in a non-torque map.
See cartodb-spatial-aggregation for more information.
Because the Torque Heatmap is a variation of the Torque map, the points of the map won't be exactly the points of your dataset, and the attributes of "Heatmap points" won't be the exact attributes of your dataset. The Heatmap creates one point for each grid cell that represents an aggregation of all the original points in that cell. The way those points are aggregated is defined in this CartoCSS line:
"count(cartodb_id)" means CARTO will count up the number of points in each grid cell.
Maybe for your use case it would be better to use a Torque Category map, where you can define a Torque map and change the size of your points depending on a category of your dataset. In this section of the CARTO Map Academy you can find more information about Heatmap and Torque maps.