No, you cannot do that. According to RFC 2828, SSL certificate wildcards can be used to match a single domain name component, not multiple components. This has been amended and further clarified in RFC 6125, which states in section 5.2 that:
o The ’*’ (ASCII 42) wildcard character is allowed in the dNSName of
the subjectAltName extension (and in common name, if used to store
the host name), but only as the left-most (least significant) DNS
label in that value. This wildcard matches any left-most DNS
label in the server name. That is, the subject *.example.com
matches the server names a.example.com and b.example.com, but does
not match example.com or a.b.example.com. Implementations MUST
support wildcards in certificates as specified above, but MAY
provide a configuration option to disable them.
In other words, multiple wildcards are not allowed, and any wildcard must be in the leftmost component of the DNS name. This is repeated in section 6.4.3, specifying how clients should behave when they encounter certificates with wildcards in them - any wildcards other than in the leftmost component of the domain name should result in the certificate not matching the domain name you're using it for. Specifically, the first point in 6.4.3 is:
1. The client SHOULD NOT attempt to match a presented identifier in
which the wildcard character comprises a label other than the
left-most label (e.g., do not match bar.*.example.net).
So, even if you could make Letsencrypt make those certificates, the visitors to your website still would not accept them.