Why "ls -a" and "find" cannot access /run/5000/ as sudo?

I have a program set that lists all things in a directory and recursively inside etc and records path, timestamps, and inode. One uses "find" and one uses "ls -a". With "find" it has permission denied for /run/5000/" and does not list subdirectories. With "ls -a" that directory is not listed, no errors, and no known to that program in accessed things. I run both with "find" and with "ls -a" as sudo on / directory. Like my goal is to record all timestamps for all things in and in in etc. / directory. Like my programs also show in terminal what is path of currently being recorded file or folder. Both programs work fine except that "/run/5000/" directory and it's contents. Is there a super-root or a better way? There is no filter except no ".." or "." for directories and folders with "ls -a" and none with "find". I use a recursive function with "ls -a" that calls itself for directories or records for anything else including symbolic links. I am not even seeing "/run/5000/" in like my recordings and during recording output to terminal does not show that directory. Programs run like "sudo ./myProgram.sh /". I am on Ubuntu desktop 22.04.3 LTS with Ubuntu Pro on a Lenovo Thinkpad T460.

Other things I should mention, icons for snap store are sometimes not found after running this and "Files" sometimes will not respond until I close it then reopen, long after recording is done. These programs I made use like 100% capacity on CPUs and not much RAM. I find closing "Files" app when it does not respond during running may cause a system crash. Nothing special about like my programs or much extra. I would rather not disclose exact code for now. All as per one might be maybe or might not be maybe, maybe or maybe not, maybe.