It’s not a type exposed to reflection (no UCLASS macro) because it’s not a type that you should probably be working directly with in blueprint. Multi-threading is hard enough in C++, it probably wasn’t worth complicating it even more to support blueprints.
Does creating actors in multiple threads improve rendering efficiency?
No, absolutely not.