What are you trying to accomplish with this? Seeing the rules and when they are running is mainly an administration function, not something you’d expose to the suers of your home automation. They shouldn’t know or care about the names and status of the rules and if there is some functionality they need to control that functionality should be modeled and exposed as Items.
You’d have to create a rule that triggers on RuleStatusInfoEvents (a generic trigger with a filter, note this is really advanced stuff but you can find an example that works with ThinStatusInfoEvents at Thing Status Reporting [4.0.0.0;5.9.9.9].
This rule will then need to update an Item(s) that gets shown on the UI. You’ll have to figure out when/how to cancel out the state of that Item(s). Properly written rules shouldn’t take more than a few hundred milliseconds to be triggered, run and then exit. For the most part one would have to be lucky to see anything change at all in the browser when a rule is running.
If you do infact have long running rules, you probably need to reassess those rules and consider using Timers instead of sleeps if that’s the root cause of the length.