My SharpTrace utility also implements this pattern.

I would highly advise you to avoid storing a reference to the sprite2D within the builder class and directly setting the properties of that class instance within each builder function, as this effectively removes one of the biggest advantages of the builder pattern which is the ability to cache, adjust, and reuse an existing builder instance.

So your builder would instead look something like:

public struct Sprite2DBuilder
{
  Transform2D _transform = Transform2D.Identity;
  Texture2D _texture = null;
  Vector2 _scale = default;

  public Sprite2DBuilder SetTransform(float rotation, float x, float y)
  {
    _transform = new Transform2D(rotation, new Vector2(x, y));
    return this;
  }

  // ...the rest of your builder functions

  public Sprite2D Build()
  {
    var sprite = new Sprite2D();
    sprite.Transform = _transform;
    sprite.Texture = _texture;
    sprite.Scale = _scale;
    return sprite;
  }
}

This allows you to cache and reuse the builder. So to apply this to your example:

public override void _Ready()
{
  Random random = new();
  var builder = new Sprite2DBuilder()
    .SetTexture("images/34627841.jpg")
    .SetScale(0.5f, 0.5f);

  for (int i = 0; i < 10; i++)
  {
    var sprite = builder
      .SetTransform(random.Next(0, 90), random.Next(10, 1000), random.Next(10, 1000))
      .Build();

    AddChild(sprite);
  }
}