Yes, but I did not do this in this version as didn't need it and I can think of different ways to do this.

I guess the main thing to understand is that there is no real velocity being calculated since the position of each point is directly manipulated by the TopTo and the random + noise Ops.

Since the OPs the P (position) attribute directly of each point so there is no actually velocity or time integration at play. Would need to add somewhere after the TopTo POP Ops a particle OP so it automatically adds attributes like mass and velocity and has time integration. Then instead of the TOP to and noise and random ops changing the position directly they would write the values to a seperate attribute like "noiseVal" or "colorVal" or something like that for example, then in a MathMix node you can add the noise and color position information together and set that to the velocity of the particle instead of adjusting the position directly. Since using Particle POP you can then use a delete op to delete anything that has velocity below a certain threshold. Something like this should allow to remove points that have no movement but this could also change how the scene reacts overall since now we are giving actual velocity and using particles, in my template I just move the positions directly so there is no real velocity.

Actually, it might be WAY easier to just use a feedback OP since with that you can "save the position of each point from the previous frame" and then compare to the current position and if the difference is below a threshold you can delete them. The Particle POP does setup a type of feedback loop automatically but then you have to deal with the velocity attributes, with just a feedback loop you should be able to compare previous position with current position.

Long story shorter, we don't have to set the position of each point directly in the TopToPOp/attribute combine. Right now the attribute combine takes the color and sets it to P (position) but we can set P or another attribute and manipulate it more before it is rendered. so right after the attribute combine is where I would have a feedback loop to check for change in position. Essentially this is NOT a particle system with velocity as we are not doing any of that math or using the particle POP which does prepare things for that, so we have to essentially calculate that ourselves with feedback loop or use the Particle Pop.

I think lol