Thanks for posting these questions. In regards of number one, yes you are right, these are bugs that have been already reported and whose fix will be included in Pulse 5.8.1.
In regards the Long Running Operations Report, it is important to keep in mind that these are logged every 60 seconds into Pulse (this setting is referred as LoggerInterval in Pulse.cfg), By setting this parameter to something smaller, you might get a more frequent refresh of the long running Threads, but at the expense of increasing the size of disk of Database of Pulse. These reports are intended for analysis after an event has occurred, for live tracking, A “Run Time Alert” would be a more adequate utility for such proposes.
Now, in regards of the Run Time and Wait Time Analysis reports, this is the desired functionality, Pulse creates a summary of the State of the TM1 Server and its Instances every 10 minutes into the knowledge base of Pulse , you can notice this interval by checking the “Start” and “End” columns and will match such interval, if an operation takes more than 10 minutes, this thread will be shown in diverse records of these reports.
 This is the default value, this can be modified in the “Administration/Configuration” page.