Surround the code you want to use with push/popMatrix i.e.

1. ...
2.  rotateX(objectRotationX);   // some object rotation
3.  for (int i = 0; i <= 10; i++){
4.    pushMatrix();
5.      translate(i,0,0); rotateX(i/10);   // or any other transforms that are changing through the loop
6.      pushMatrix();
   
7.      // need global coordinates of 'current' position here to add some analysis
8.      // Safe to perform any matrix operations e.g. ressetMatrix / applyMatrix
   
9.      popMatrix();
   
10.      point(0,0,0);                          // this would be the point in question
11.    popMatrix();
12.  }
13. // i need to be back in objectRotationX here
14. ...

Alternatively you could get a copy of the current model view matrix i.e.

1. ...
2.  rotateX(objectRotationX);   // some object rotation
3.  for (int i = 0; i <= 10; i++){
4.    pushMatrix();
5.      translate(i,0,0); rotateX(i/10);   // or any other transforms that are changing through the loop
6.      PMatrix mat = new PMatrix3D();
7.      getMatrix(mat);
8.      // need global coordinates of 'current' position here to add some analysis
9.      // mat is a copy of the modelview matrix so safe to use in anyway you want
   
10.      point(0,0,0);                          // this would be the point in question
11.    popMatrix();
12.  }
13. // i need to be back in objectRotationX here
14. ...

I could be wrong and I probably am but I thought resetMatrix sets the matrix back to the identity matrix but I could be wrong.

I just checked the reference for resetMatrix and I am glad to say that I was right and it should not clear the transformation stack.

As to seem to be aware, the whole point of the pushMatrix/popMatrix operations is so that the transformation matrix can be manipulated safely because it can be restored to its previous configuration. In your first post you said you wanted a non-destructive way of accessing and manipulating the current transformation matrix, both techniques in my previous post will do that.