Out of the box, no, what you're asking isn't possible.
There is more than one reason.
Reason #1
By default, there's an Enumerable.Select method that has two parameters. One of Type T (the enumerable member) and one of type int (the index).
This reason is why you receive:
// CS0019 Operator '+' cannot be applied to operands of type 'UserQuery.Point' and 'int'
Reason #2
The second reason this isn't possible is the notion of deconstruction doesn't apply to parameter creation.
For instance:
var (x, y) = myPoint;
Is different than the lambda syntax of:
var myPointSumQuery = myPoints.Select((x, y) => x + y);
Conclusion
There's no built-in way for the compiler to know 'Hey they want to deconstuct this enumerable series into parameters'.
You get close with the following:
var p = new Point(3, 3);
var p2 = new[] { p };
var p3 = p2.Select(x => (x.X, x.Y)).Select(((int x, int y) e) => e.x + e.y);
But if you notice, you end up with the same problem of X and Y needing to be contained within the parameter 'e'.
There was discussion along these lines which would get you closer if you see the following link: Proposal: Tuple deconstruction in lambda argument list
It seems that it was never implemented, because this is illegal:
var p3 = p2.Select(x => (x.X, x.Y)).Select(((int x, int y)) => x + y);
Since C# cannot deconstruct tuples into parameters, the extended notion of 'Deconstruct the each point's members into parameters' would not work, either.