In general, AND gates are no big deal. In practice however, many zero-knowledge systems are based on rank-1-constraint systems (R1CS, often "arithmetic circuits" in folklore), and the concern that LowMC tries to address is linked to this practicality. Note that I'm talking from the perspective of ZK, although the principles probably carry over to FHE and MPC.
In R1CS, you declare constraints between inputs and outputs, and these constraints are of arithmetic form. For instance, you would write "(input[0] + 1)*secret[0] = output[0]". In most R1CS systems (read: all that I know of), it is the multiplication gates that weigh heavy in the prove/verify functions, and the additions mostly come for free.
Now, most encryption/decryption functions are defined in terms of bitwise operations, not in terms of + and *.
To prove that you know the decryption of a certain value and its associated key, you would thus need to convert all those bitwise operators into arithmetic operations. You can imagine these equations become quite large. The main operations in this context are, as you correctly identified, AND, OR and XOR. Depending on the convention you use, you will encode True as 1 and False as 0, or vice versa. It is then relatively easy to see that x AND y becomes $x * y$ and x XOR y becomes $x + y - 2 * x * y$, and x OR y becomes $x + y - x * y$.
Now, there are quite some optimizations that you can carry out here. For example, if you would use a stream cipher to show decryption, then you have to XOR your cipher stream $s[..]$ with the cipher text $c[..]$. The former is a result of your circuit, but often the latter is a public value. If this is the case, you can make that specific XOR more efficient by doing something like
let xor = if c[i] == 0 {
s[i]
} else {
1 - s[i]
};
which requires no multiplications for this specific XOR.
A related optimization exists for OR: if you take the convention False as 0, True as anything else, then x OR y just becomes $x + y$, as long as your field is large enough.
TL;DR: AND becomes multiplication, multiplication costs processing time. XOR can sometimes be optimized out a bit. By the way, if you're interested in low-multiplier-count symmetric crypto, have a look at Poseidon too!