Stateless firewall filters on SRX serve at least a few purposes:
First, they can be a good first line of defense on your SRX for common types of traffic that perhaps you do not want your SRX wasting valuable session table space for. The stateless filter is processed prior to any screens, NAT, or security policies. I use firewall filters on some of our SRX devices to block blacklisted IP addresses or common ports used by script kiddies for worm propagation (SQL, Netbios, etc.).
Second, they can and should be used to protect the routing engine from unauthorized access. Even though you may have defined certain protocols and services to run on your SRX, you still need to prevent unauthorized access from non-permitted IP addresses. In addition, the security policies on the SRX only work on transit traffic, not traffic that terminates on the SRX device itself. Therefore, a routing engine firewall filter that is applied to the loopback interface is a necessity for a fully secure configuration.
The third most common use of stateless firewall filters is for multifield classification, which is used in class of service for traffic identification.
There are certainly other reasons for using firewall filters, but I'd say these are the most common.